ISSUE ABEND in response to SYNCPOINT

In an APPC mapped conversation, a transaction issues a SYNCPOINT command and its partner responds with an ISSUE ABEND command.

Figure 1 illustrates an ISSUE ABEND command being used in response to SYNCPOINT 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. You can also send ISSUE ABEND before receiving SYNCPOINT; but this is not shown, because the results are the same.
Figure 1. ISSUE ABEND 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 an ISSUE ABEND command; theabend indication is transmitted; transaction B's conversation is in free state .
  4. Transaction A abends with code ASP3.
  5. Transaction B issues a FREE command to free its conversation with transaction A.
  6. 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, when an ISSUE ABEND command is issued in response to a SYNCPOINT command on an APPC mapped conversation.


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