Emergency restart backout
If a CICS® region fails, you restart CICS with an emergency restart to back out any transactions that were in-flight at the time of failure.
During emergency restart, the recovery manager uses the system log data to drive backout processing for any units of work that were in-flight at the time of the failure. The backout of units of work during emergency restart is the same as a dynamic backout; there is no distinction between the backout that takes place at emergency restart and that which takes place at any other time. At this point, while recovery processing continues, CICS is ready to accept new work for normal processing.
- The backout processing for any units of work that were in a backout-failed state at the time of the CICS failure
- The commit processing for any units of work that had not finished commit processing at the time of failure (for example, for resource definitions that were being installed when CICS failed)
- The commit processing for any units of work that were in a commit-failed state at the time of the CICS failure
See Unit of work recovery for an explanation of the terms commit-failed and backout-failed.
The recovery manager drives these backout and commit processes because the condition that caused them to fail might be resolved by the time CICS restarts. If the condition that caused a failure has not been resolved, the unit of work remains in backout- or commit-failed state. See Backout-failed recovery and Commit-failed recovery for more information.