Recovering IMSRSC repository data sets when no IMS systems or RM systems are active

You can recover IMSRSC repository data sets when all IMS systems and RM systems are down and no IMS log is available but backup copies of the repository data sets are available.

Any IMS IDs that were deleted from the IMSRSC repository using the DELETE DEFN TYPE(IMSIDMBR) command after the repository backup was taken will now be in the IMSRSC repository. If the resource definitions for the IMS ID and the IMS IDs are no longer needed in the IMSRSC repository you must reissue the DELETE DEFN TYPE(IMSIDMBR) command.

Procedure

  1. Define the primary and secondary data sets from the backup copies.
  2. Start the repository by using the FRPBATCH START command or the F reposervername,ADMIN START command.
    The repository is started from the backup copies of data.
  3. List the repository information by using the FRPBATCH LIST command or the F reposervername,ADMIN DISPLAY command.
  4. Cold start IMS systems from the repository.
  5. To bring the repository and IMS systems to the same state as the time of failure, reissue the commands that you used to create, update, or delete the resource definitions between the time the backup was generated and the IMS cold start.
    The type-1 or type-2 commands that were issued from OM API can be obtained from the OM audit log or command responses sent to OM API.
Any new IMS change lists in the IMSRSC repository that are created after the backup time are lost. To re-create these IMS change lists, you must reissue the IMPORT DEFN commands that created them.

Any old IMS change lists in the backup data sets exist in the IMSRSC repository. If any of these lists are not needed because IMS was restarted or a DEL DEFN TYPE(CHGLIST) command was issued, you must issue the DEL DEFN TYPE(CHGLIST) command to delete the residual change lists that are no longer needed.