Recovering from failures

The following topics provide information to help you plan for an recover from failures in a data-sharing environment.

Managing system logs
Recovering a shared database requires log data from each sharing IMS system. A DBRC GENJCL.RECOV command or a Database Recovery utility execution using DBRC will fail if logs need to be merged for the database.
Planning recovery procedures
Recovery in a data-sharing environment is similar to standard IMS recovery.
Recovery facilities
Dynamic backout, batch backout, and forward recovery facilities are different in data-sharing and nonsharing environments.
Recovery without DBRC
If you perform any recovery-related actions when DBRC is not running, such as making database image copies, problems could arise because DBRC would be unaware of changes in status. You must, therefore, specifically inform DBRC of such changes.
Restart after IMS failure
Restart an IMS system in a data-sharing environment in the same way as in a nonsharing environment.
Restart after DBRC failure
Because DBRC runs under the control of IMS, if IMS abnormally terminates, IMS tries to release DBRC buffers, and to close the system log.
Recovery involving IRLM
Failure in one part of a data-sharing configuration does not usually cause the other parts to fail.

Parent topic: Data sharing in IMS environments