Session failure in response to SYNCPOINT

In an APPC mapped conversation, a transaction issues a SYNCPOINT command, its partner responds with a SYNCPOINT command, but the session fails before the first transaction receives the response.

Figure 1 and Figure 2 illustrate what happens if the session fails before or after a SYNCPOINT command issued in response to SYNCPOINT on an APPC mapped conversation. The figures also show the conversation state before each command and the state and EIB fields set after each command.
Figure 1. Session failure before SYNCPOINT in response to SYNCPOINT 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 .
  1. Transaction A issues a SYNCPOINT command; the syncpoint request is transmitted, and the transaction is suspended until a response is received from transaction B.
  2. Transaction B issues a RECEIVE command which returns control immediately; EIBSYNC and EIBRECV are set, and its conversation is in syncreceive state .
  3. The session between transaction A and transaction B fails.

    From this point , the two transactions are independent of one another.

  4. Transaction B issues a SYNCPOINT command; its conversation is freed, and a NOTALLOC condiition is raised for any further commands that attempt to use the conversation.
  5. Transaction A abends with code ASP3.
This figure shows the state changes, and the EIB flags that are set, as the result of a session failure before a SYNCPOINT command is issued in response to a SYNCPOINT command on an APPC mapped conversation.
Figure 2. Session failure after SYNCPOINT in response to SYNCPOINT 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 .
  1. Transaction A issues a SYNCPOINT command; the syncpoint request is transmitted, and the transaction is suspended until a response is received from transaction B.
  2. Transaction B issues a RECEIVE command which returns control immediately; EIBSYNC and EIBRECV are set, and its conversation is in syncreceive state .
  3. Transaction B issues a SYNCPOINT command; the response is transmitted, and its conversation is in receive state .
  4. The session between transaction A and transaction B fails.

    From this point , the two transactions are independent of one another.

  5. Transaction A abends with code ASP3.
  6. Transaction B issues a RECEIVE command which returns control immediately; EIBERR and EIBFREE are set, and its conversation is in free state .
  7. Transaction B issues a FREE command to free its conversation with transaction A.
  8. Transaction B issues a SYNCPOINT ROLLBACK command in order that its resources remain consistent with transaction A's resources.
This figure shows the state changes, and the EIB flags that are set, as the result of a session failure after a SYNCPOINT command is issued in response to a SYNCPOINT command on an APPC mapped conversation


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