Re-establishing database integrity

If no emergency restart succeeds, an appropriate response depends on your understanding the reason for the failure. Although it might not work exactly as written for your installation, use the following procedure to reestablish database integrity.

1. Run the Log Recovery utility (DFSULTR0) to close the OLDS (CLS mode). If the utility needs additional logs, concatenate them in your JCL, oldest first, and rerun the utility.
2. Be sure that your log is correct and that your databases are consistent with the log.
3. Produce an SLDS using the Log Archive utility (DFSUARC0).
4. Forward recover all updated DEDBs to make them consistent with the log using the Database Recovery utility (DFSURDB0).
   Recommendation: If the recovered area utilized the shared VSO option, ensure that there are no failed-persistent XES connections to the CF structure used by the area. If necessary, use the z/OS® SETXCF command to delete the connections prior to cold start of the systems involved.
5. For full-function databases, run the Batch Backout utility (DFSBBO00) to back out programs (PSBs) that were active at the time of failure. Determine these from the output of the Log Recovery utility.
6. Update the RECON data set, if necessary, to reflect the current status of the system.
7. If you use MSDBs, rebuild the MSDBINIT data set from the last used MSDBCP1 and MSDBCP2 data sets and the last SLDS.