Session failure in response to SYNCPOINT ROLLBACK
In an APPC mapped conversation, a transaction issues a SYNCPOINT ROLLBACK command, its partner responds with a SYNCPOINT ROLLBACK command, but the session fails before the first transaction receives the response.
Figure 1
illustrates what happens if the session
fails after SYNCPOINT ROLLBACK is received and before the response is
issued
on an APPC mapped conversation. The figure also shows the conversation
state
before each command and the state and EIB fields set after each command.
Figure 1. Session failure during SYNCPOINT ROLLBACK in response
to SYNCPOINT ROLLBACK on an APPC mapped conversation. 
In this
figure, transaction A is communicating with transaction B using an APPC
mapped
conversation. Initially, transaction A's conversation with B is in
send
state
, and transaction B's conversation with A is in
receive
state
.
- Transaction A issues a SYNCPOINT ROLLBACK command; the rollback request is transmitted, and the transaction is suspended until a rollback response is received from transaction B
- Transaction B issues a RECEIVE command which returns control immediately; EIBERR and EIBSYNRB are set, and its conversation is in rollback state .
- The session between transaction A and transaction B fails.
From this point , the two transactions are independent of one another.
- Transaction B issues a SYNCPOINT ROLLBACK command; its conversation is in free state .
- Transaction A's SYNCPOINT ROLLBACK command completes; its conversation is in free state .
