SYNCPOINT ROLLBACK in response to SYNCPOINT

In a complex distributed transaction, during sync point processing, one of the agents determines that the transaction should be backed out.

Figure 1 shows the sequence of events for a sync point involving six conversing transactions, when one of the agents determines that the distributed transaction should be backed out. The topology, and initial states are the same as in Figure 1 :
Transaction A
  • is in conversation with transactions B and D. Before the syncpoint, its conversations with B and D are in send state.
  • is the sync point initiator with respect to transactions B and D.
Transaction B
  • is in conversation with transactions A, C, and E. Before the syncpoint, its conversation with A is in receive state, and its conversations with C and E are in send state.
  • is a sync point agent of transaction A, and the sync point initiator with respect to transactions C and E.
Transaction C
  • is in conversation with transaction B. Before the syncpoint, its conversation with B is in receive state.
  • is a sync point agent of transaction B.
Transaction D
  • is in conversation with transactions A and F. Before the syncpoint, its conversation with A is in receive state, and its conversation F is in send state.
  • is a sync point agent of transaction A, and the sync point initiator with respect to transaction F.
Transaction E
  • is in conversation with transaction B. Before the syncpoint, its conversation with B is in receive state.
  • is a sync point agent with respect to transaction B.
Transaction F
  • is in conversation with transaction D. Before the syncpoint, its conversation with D is in receive state.
  • is the only sync point agent of transaction D.
Figure 1. Rollback during distributed syncpointing
This figure shows the interactions and state changes during a sync point in a distributed transaction, when one of the agents determines that the transaction should be backed out.

As in Figure 1 , transaction A (while in send state , state 2) issues the SYNCPOINT command, and CICS® initiates a chain of events. Here, however, transaction E has detected an error that makes it unable to commit, and it issues SYNCPOINT ROLLBACK when it detects that the conversation on its principal facility is in syncreceive state (state 9, EIBSYNC is also set). This causes any changes that transaction E has made to be backed out, and initiates a distributed rollback.

Transactions B, C and A are rolled back (EIBRLDBK set). Transaction D senses that the conversation on its principal facility is in rollback state (state 13, EIBSYNRB is also set), and issues a SYNCPOINT ROLLBACK command. Transaction F too senses that the conversation on its principal facility is in rollback state , and issues a SYNCPOINT ROLLBACK command. The distributed rollback is now complete.



dfhp633.html | Timestamp icon Last updated: Monday, 5 June 2017