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).

If you are not able to complete forward recovery on a data set, ensure that all CICS regions tidy up any pending recovery processing on the data set (as described below) before you restore the backup copy from which you intend to work. You can do this in the following way:

  1. 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.
  2. If there are shunted in-doubt UOWs, try to resolve the in-doubts before proceeding to the next step. This is because the in-doubt UOWs may have updated resources other than the failed data set, and you don’t want to corrupt these other resources.
  3. In all CICS regions that could have updated the failed data set:
  4. 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.

[[ Contents Previous Page | Next Page Index ]]