Procedure for failed non-RLS mode forward recovery operation
If you are not successful in applying all the forward recovery log data to a restored backup, you are forced to abandon the forward recovery, and revert to your most recent full backup.
However, during its recovery processing, CICS® assumes that it is operating on a data set that has been correctly forward recovered, as in the case of recovery of a data set accessed in RLS mode (see Procedure for failed RLS mode forward recovery operation).
- Make sure that any CICS regions that are not running, and which could have updated the data set, are restarted to enable emergency restart processing to drive outstanding backouts.
- If there are shunted indoubt units of work, try to resolve the in-doubts before proceeding to the next step. This is because the indoubt units of work may have updated resources other than the failed data set, and you don’t want to corrupt these other resources.
- In all CICS regions that could have updated the failed
data set:
- Force shunted indoubt units of work using set DSNAME(…) UOWACTION(COMMIT
| BACKOUT | FORCE).
Before issuing the next command, wait until the SET DSNAME(…) UOWACTION has completed against all shunted indoubt units of work.
- Reset locks for backout-failed units of work using SET DSNAME(…)
RESETLOCKS.
Do not issue this command until the previous UOWACTION command has completed. RESETLOCKS operates only on backout-failed units of work, and does not affect units of work that are in the process of being backed out. If you issue RESETLOCKS too soon, and shunted indoubt units of work fail during backout, the data set will be left with recovery work pending.
- Force shunted indoubt units of work using set DSNAME(…) UOWACTION(COMMIT
| BACKOUT | FORCE).
- Finally, when you are sure that all CICS regions have completed any recovery work for the data set, restore the backup.
If you do not follow this sequence of operations, the restored backup could be corrupted by CICS backout operations.