Recovering IMSRSC repository data sets when one or more IMS systems are down but an RM system is active

You can recover IMSRSC repository data sets when one or more IMS systems are down but IMS logs are available and an RM system is active.

1. Define new primary and secondary repository data sets for a repository that failed, by using the FRPBATCH UPDATE command.
2. Start the repository by using the FRPBATCH START command or the F reposervername,ADMIN START command.
3. List the repository information by using the FRPBATCH LIST command or the F reposervername,ADMIN DISPLAY command.
4. Write the resource definitions to the repository by performing one of the following steps:
   • If your IMS systems are cloned, route the following command to one of the active IMS systems in the IMSplex and have it write its resource definitions to the repository for all of the IMS systems in the IMSplex.

     EXPORT DEFN TARGET(REPO) TYPE(ALL) NAME(*) SET(IMSID
     (IMSids_of_all_IMSs_sharing_repository))

   • If your IMS systems are not cloned, take one of the following steps:
     • Issue the EXPORT DEFN TARGET(REPO) TYPE(ALL) NAME(*) command at each active IMS system to route the command to each active IMS system in the IMSplex. This command writes the runtime resource definitions from each active IMS to the repository.
     • Generate a resource definition data set (RDDS) for each IMS system that is down. The RDDS can be generated from the IMS logs by using the DFSURCL0 utility. Then, run the CSLRUP10 utility to write the resource definitions from each generated RDDS to the repository.