Transaction backout

If the resources updated by a failed unit of work are defined as recoverable, CICS® automatically performs transaction backout of all uncommitted changes to the recoverable resources.

Transaction backout is mandatory and automatic - there is not an option on the transaction resource definition allowing you to control this. You can, however, control backout of the resources on which your transactions operate by defining whether or not they are recoverable.

In transaction backout, CICS restores the resources specified as recoverable to the state they were in at the beginning of the interrupted unit of work (that is, at start of task or completion of the most recent synchronization point). The resources are thus restored to a consistent state.

In general, the same process of transaction backout is used for individual units of work that abend while CICS is running and for in-flight tasks recovered during emergency restart. One difference is that dynamic backout of a single abnormally terminating transaction takes place immediately. Therefore, it does not cause any active locks to be converted into retained locks. In the case of a CICS region abend, in-flight tasks have to wait to be backed out when CICS is restarted, during which time the locks are retained to protect uncommitted resources.

To restore the resources to the state they were in at the beginning of the unit of work, CICS preserves a description of their state at that time:
  • For tables maintained by CICS, information is held in the tables themselves.
  • For recoverable auxiliary temporary storage, CICS maintains information on the system log about all new items written to TS queues. CICS maintains information about TS queues for backout purposes in main storage.
  • For transient data, CICS maintains cursors that indicate how much has been read and written to the queue, and these cursors are logged. CICS does not log before- or after-images for transient data.
  • For CICS files, the before-images of deleted or changed records are recorded in the system log. Although they are not strictly "before-images", CICS also logs newly added records, because CICS needs information about them if they have to be removed during backout.


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