Unit of work recovery and abend processing

A number of different events can cause the abnormal termination of transactions in CICS.
These events include:
  • A transaction ABEND request issued by a CICS® management module.
  • A program check or operating system abend (this is trapped by CICS and converted into an ASRA or ASRB transaction abend).
  • An ABEND request issued by a user application program.
  • A CEMT, or EXEC CICS, command such as SET TASK PURGE or FORCEPURGE.
    Note: Unlike the EXEC CICS ABEND command, these EXEC CICS commands cause other tasks to abend, not the one issuing the command.
  • A transaction abend request issued by DFHZNEP or DFHTEP following a communication error. This includes the abnormal termination of a remote CICS during processing of in-flight distributed UOWs on the local CICS.
  • An abnormal termination of CICS, in which all in-flight transactions are effectively abended as a result of the CICS region failing.

    In-flight transactions are recovered during a subsequent emergency restart to enable CICS to complete the necessary backout of recoverable resources, which is performed in the same way as if the task abended while CICS was running.



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