Creating MODBLKS resource and descriptor definitions in the IMSRSC repository

You can create MODBLKS resource and descriptor definitions in the IMSRSC repository for one or more new or existing IMS systems in your IMSplex.

1. Define the IMSRSC repository.
2. Create the MODBLKS resource and descriptor definitions in the repository for one or more IMS systems by using one of the following procedures:
   • Run the RDDS to Repository utility (CSLURP10) by using a generated RDDS. Specify IMSPLEX(NAME=plxnm IMSID(imsx)).

     In the JCL, imsx is the list of one or more IMS IDs in the IMSplex that the CSLURP10 utility populates in the repository. The IMS IDs that you specify can be for either new or existing IMS systems.

     Use the system RDDS generated by IMS at system checkpoint, or generate the RDDS with one of the following methods:

     • By using an EXPORT DEFN TARGET(RDDS) command
     • From the IMS logs, by using the CSLURCL0 utility
     • From MODBLKS, by using the CSLURCM0 utility
   • Export the resource and descriptor definitions from an active IMS system by using the EXPORT DEFN TARGET(REPO) NAME(*) TYPE(ALL) command.

     If you are creating resource and descriptor definitions in the repository for a single IMS system or for multiple IMS systems that each need a unique set of definitions, issue the EXPORT DEFN TARGET(REPO) NAME(*) TYPE(ALL) command. In a non-cloned environment, the EXPORT DEFN TARGET(REPO) command must be issued to each IMS for which the resource definitions and descriptors are to be exported to the repository. Because the EXPORT DEFN TARGET(REPO) command is processed only by the command master IMS, a separate EXPORT DEFN TARGET(REPO) command must be issued to each IMS system. You can use the ROUTE keyword on the OM API to specify the IMS to which the command is routed. You do not have to specify the SET(IMSID()) keyword, because IMS defaults the IMS ID to the command master IMS.

     If you are creating resource and descriptor definitions in the repository for multiple IMS systems with the same set of definitions, issue the EXPORT DEFN TARGET(REPO) NAME(*) TYPE(ALL) command with the option SET(IMSID(imslist)). In the command, imslist is the list of IMS IDs of one or more IMS systems in the IMSplex for which the resource and descriptor definitions are to be created in the repository. An IMS resource list containing the definitions is created in the repository for each IMS listed in imslist.

   • To create resource and descriptor definitions in the repository for a new IMS system that has not yet been cold started, perform the following steps:
     1. Start IMS by obtaining the resource definitions from the MODBLKS data set, or a system RDDS, or you can come up with no resources and use the CREATE commands to create resource definitions after the IMS cold start.
     2. After the IMS cold start, when all resource and descriptor definitions have been created, issue the EXPORT DEFN TARGET(REPO) command with options NAME(*) TYPE(ALL) to export the resource and descriptor definitions from IMS to the repository. The EXPORT DEFN TARGET(REPO) command must be routed to the IMS system for which the resource and descriptor definitions are to be exported, by using the ROUTE keyword on the OM API.
3. If one or more IMS systems in the IMSplex consist of remote transactions and MSC is defined, the SIDR and SIDL values in the repository might not be correct. In this case, perform the following steps:
   1. If the IMS system is cold started from the repository, update the SIDR and SIDL values at each IMS by issuing the UPDATE TRAN SET(SIDR(),SIDL(),REMOTE()) command for the IMS system.
   2. Update the remote transaction definitions in the repository by issuing the EXPORT DEFN TARGET(REPO) command with options NAME(rmttrannames) TYPE(TRAN).