Emergency termination of a conversation
The ISSUE ABEND command provides a means of abnormally ending the conversation. It is valid for all levels of synchronization, but should be avoided at sync level 2, because its use at the wrong time can lead to a loss of data integrity.
ISSUE ABEND can be issued by either transaction, irrespective of whether it is in send or receive state, at any time after the conversation has started. For a conversation in send state (state 2), any deferred data that is waiting for transmission is flushed before the ISSUE ABEND command is transmitted.
The transaction that issues the ISSUE ABEND command is not itself abended. It must, however, issue a FREE command for the conversation unless it is designed to terminate immediately.
If an ISSUE ABEND command is issued in receive state (state 5), CICS purges all incoming data until an INVITE, syncpoint request, or LAST indicator is received. If LAST is received, no abend indication is sent to the partner transaction.
If an ISSUE ABEND is received, CICS abends the transaction with abend code AZCH, sets on EIBERR(= X'FF' ),EIBFREE(= X'FF' ), and places X'0864' in the first two bytes of EIBERRCD.