Demanding INVITE from the partner transaction
If a transaction needs to send an immediate error notification to the partner transaction it can use the ISSUE ERROR command.
This command is also one of the preferred negative responses to SEND CONFIRM. However it should not be used to reject ISSUE PREPARE, SYNCPOINT or SYNCPOINT ROLLBACK. When the ISSUE ERROR is received, EIBERR= X'FF' and the first two bytes of EIBERRCD are X'0889' . This error condition cannot be processed by HANDLE CONDITION (or RESP).
If an ISSUE ERROR command is used in receive state (state 5), all incoming data is purged until an INVITE, SYNCPOINT, or LAST command is received. If LAST is received, no error indication is sent to the partner transaction, EIBFREE= X'FF' and the conversation is switched to free state (state 12).
If LAST is not received, the conversation is switched to send state (state 2). It is normal programming practice to communicate the reason for the ISSUE ERROR to the partner transaction. The CONVERSE command could be used to send an appropriate error message and receive a reply.
Because ISSUE ERROR is allowed in both send state (state 2) and receive state (state 5), it is possible for both communicating transactions to use ISSUE ERROR at the same time. When this occurs, only one of the ISSUE ERROR commands is effective. The other is purged with incoming data. However both ISSUE ERROR commands will appear to have completed successfully and the transaction whose ISSUE ERROR was purged will pick up EIBERR= X'FF' on a subsequent command.