Scratching and repopulating the IMSRSC repository data sets

If an IMSRSC repository error occurs with no backup IMSRSC repository, you need to scratch and repopulate your IMSRSC repository data sets.

In different conditions, perform the following steps to scratch only the IMSRSC repository data sets, not the IMSRSC repository catalog data sets, and repopulate the IMSRSC data sets from IMSs or RDDSs.

Table 1. Scratching and repopulating the IMSRSC repository data sets
Condition IMS systems are not cloned IMS systems are cloned
IMS is active Route the following EXPORT command to the IMS to populate the repository with the IMS's resource definitions: 
EXPORT DEFN TARGET(REPO) 
NAME(*) TYPE(ALL)
A separate EXPORT command must be issued for each IMS.		 Route the following EXPORT command to one of the IMSs:
EXPORT DEFN TARGET(REPO) 
NAME(*) TYPE(ALL) 
SET(IMSID(ims1,ims2,...))
The IMSID list must contain the IMSID of each IMS in the IMSplex, which uses the IMSRSC repository, including the IMSIDs of any IMSs that are not active.
IMS is not active Use the DFSURCL0 utility to create an RDDS from the IMS's log records and then use the CSLURP10 utility to populate the repository with the definitions from the RDDS.

The CSLURP10 IMSID() input parameter specifies the IMSID of the IMS system, for which the resource definitions are being written to the repository.

Use the DFSURCL0 utility to create an RDDS from one of the IMS's log records. Then use the CSLURP10 utility to populate the repository for all of the IMSs in the IMSplex, which use the IMSRSC repository, by listing all of the IMSIDs on the CSLURP10 IMSID() input parameter.

You can also see CSLURLFL procedure about how to load the IMSRSC repository from IMS log records in one job.