Exporting MODBLKS resource and descriptor definitions to an IMSRSC repository

You can export resource and descriptor definitions from IMS to an IMSRSC repository by using the automatic export function or by issuing the EXPORT DEFN TARGET(REPO) command. You can export resource and descriptor definitions from the IMS system to the repository and have them defined for one or more new or existing IMS systems in your IMSplex.

Alternatively, you can use the RDDS to Repository utility (CSLURP10) to write resource and descriptor definitions from a specified RDDS (instead of exporting from IMS) to the repository.

Before exporting resource and descriptor definitions to the repository, enable the IMSplex to use dynamic resource definition (DRD) with a repository.

To check for and identify which resource and descriptor definitions have not yet been exported to the repository, issue the QUERY rsc_type SHOW(EXPORTNEEDED) command, where rsc_type can be one of the following resources and resource descriptors: DB, DBDESC, PGM, PGMDESC, RTC, RTCDESC, TRAN, or TRANDESC.

The exported resource and descriptor definitions overwrite the existing definitions in the repository for the IMS. If the EXPORT command or the CSLURP10 utility is issued with SET(IMSID(imsidlist)), the resource definitions for the IMS IDs in the IMS list are updated with the specified resource definitions. If the EXPORT command or the CSLURP10 utility is issued with SET(IMSID(*)), the resource definitions for all IMS systems are overwritten with the specified definitions.

Definitions for IMS resources such as the Fast Path utility (DBF#FPU0) and the IMS defined descriptors (DBFDSRT1, DFSDSDB1, DFSDSPG1, and DFSDSTR1) cannot be exported.

Exporting resource and descriptor definitions with automatic export

If IMS is enabled with the IMSRSC repository and AUTOEXPORT=AUTO or REPO is specified in the DFSDFxxx PROCLIB member, IMS will automatically export any changes in resource definitions for MODBLKS resources since the last automatic export or the EXPORT DEFN TARGET(REPO) command to the repository. Automatic export to the IMSRSC repository processing is done at the end of an IMS checkpoint for a normal checkpoint and before the IMS shutdown checkpoint. Any newly created or updated resources or descriptors since the last successful export are exported to the repository.

At a normal checkpoint, the newly created or modified resources will be marked in the IMS checkpoint log record as export needed. At the end of the automatic export to the repository, a new X'22' automatic export completed log record will be written.

For any errors during automatic export that was triggered by a normal checkpoint processing, you can issue the QUERY rsc_type SHOW(EXPORTNEEDED) command to see if any resource or descriptor definitions need to be exported. rsc_type can be one of the following resources and resource descriptors: DB, DBDESC, PGM, PGMDESC, RTC, RTCDESC, TRAN, or TRANDESC. Then, you can issue an EXPORT DEFN OPTION(CHANGESONLY) command or wait for the next automatic export.

If the automatic export is triggered at all IMS systems at the same time, for example through a /CHECKPOINT command that is sent to all IMS systems, it is possible that automatic export processing at one or more IMS systems might fail.

Exporting resource and descriptor definitions with the EXPORT command

Perform the following procedure to export resource and descriptor definitions to the repository:

  1. Issue the EXPORT DEFN TARGET(REPO) command. Use the parameters for the EXPORT command to specify the particular runtime resource and descriptor definitions to export to the repository.

    If you are exporting 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 exporting resource and descriptor definitions to 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.

    Resource and descriptor definitions are written to the repository during EXPORT command processing.

  2. To verify whether there are any resources that have not been exported to the repository, issue the QUERY rsc_type SHOW(EXPORTNEEDED) command, where rsc_type can be one of the following resources and resource descriptors: DB, DBDESC, PGM, PGMDESC, RTC, RTCDESC, TRAN, or TRANDESC. Then, if necessary, issue the EXPORT DEFN TARGET(REPO) command again.