CICS backward recovery (backout)
Backward recovery, or backout, is a way of undoing changes made to resources such as files or databases.
Backout is one of the fundamental recovery mechanisms of CICS®. It relies on recovery information recorded while CICS and its transactions are running normally.
- In the event of failure of an individual in-flight transaction, which CICS backs out dynamically at the time of failure (dynamic transaction backout)
- In the event of an emergency restart, when CICS backs out all those transactions that were in-flight at the time of the CICS failure (emergency restart backout).
Although these occur in different situations, CICS uses the same backout process in each case. CICS does not distinguish between dynamic backout and emergency restart backout. See CICS emergency restart for an explanation of how CICS reattaches failed in-flight units of work in order to perform transaction backout following an emergency restart.
Each CICS region has only one system log, which cannot be shared with any other CICS region. The system log is written to a unique MVS™ system logger log stream. The CICS system log is intended for use only for recovery purposes, for example during dynamic transaction backout, or during emergency restart. It is not meant to be used for any other purpose.
CICS supports two physical log streams - a primary and a secondary log stream. CICS uses the secondary log stream for storing log records of failed units of work, and also some long running tasks that have not caused any data to be written to the log for two complete activity key points. Failed units of work are moved from the primary to the secondary log stream at the next activity keypoint. Logically, both the primary and secondary log stream form one log, and as a general rule are referred to as the system log.