ISSUE ERROR in response to SYNCPOINT

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

Figure 1 illustrates an ISSUE ERROR 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 ERROR before receiving SYNCPOINT; but this is not shown, because the results are the same.

It is pointless to use ISSUE ERROR as a response to SYNCPOINT, because this causes the syncpoint initiator to discard all data transmitted with the ISSUE ERROR by the syncpoint agent. To safeguard integrity, the syncpoint agent has to issue a SYNCPOINT ROLLBACK command.

Note that if transaction A were running on a CICS® release earlier than 3.2, the results would be different.
Figure 1. ISSUE ERROR 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 ERROR command; its conversation is in send state .
  4. Transaction B issues a SEND INVITE WAIT command; the error indication and the INVITE flag are transmitted to transaction A; transaction B's conversation is in receive state .
  5. On behalf of transaction A, CICS sends a rollback request to transaction B.
  6. Transaction B issues a RECEIVE command which returns control immediately; EIBERR and EIBSYNRB are set, and its conversation is in rollback state .
  7. Transaction B issues a SYNCPOINT ROLLBACK command; the rollback response is transmitted; transaction B's conversation is restored to the state it was in at the start of the unit of work.
  8. Transaction A's SYNCPOINT command completes; EIBRLDBK is set; transaction A's conversation is restored to the state it was in at the start of the unit of work.
This figure shows the state changes, and the EIB flags that are set, when an ISSUE ERROR command is issued in response to a SYNCPOINT command on an APPC mapped conversation.


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