Create IMS.PROCLIB and IMS.JOBS members for the new IMS subsystem

Before you clone an IMS subsystem for the first time, IMS.PROCLIB and IMS.JOBS members must be created for the new, or target, IMS subsystem.

IMS Cloning Tool copies the source IMS.PROCLIB and IMS.JOBS data sets to the target volumes, and rename them. The recommendation is to place the PROCLIB and JOBS members for the target IMS subsystem into the source IMS.PROCLIB or IMS.JOBS. This ensures that the new PROCLIB and JOBS members are also copied during the cloning process by IMS Cloning Tool and available for your target subsystem.

The new IMS subsystem requires new JCL members to be created in order to be able to run in the same SYSPLEX as the source IMS subsystem. The PROCLIB and JOBS members that you need to create depend on the IMS components that the source IMS uses and the desired components for the target IMS. Additionally, some IMS parameters and configuration options can be defined differently for the new, or target, IMS subsystem to use.

In many cases, you can create the PROCLIB and JOBS members for the new IMS subsystem by creating a copy of the corresponding member in the same source data set, and editing it to change configuration information.

Create the following PROCLIB members needed for the new IMS subsystem:
  • A member to start the IMS control region address space
  • A member to start the DBRC address space
  • A member that is used by IMS for submitting jobs to the internal reader
  • An IMS control region execution parameter block, DFSPBxxx, where xxx is the RGSUF to be used for the new IMS subsystem. For this member, you must:
    1. Review the options for the target IMS system.
    2. Change APPLIDx values, if applicable.
    3. If a separate CSL environment is going to be used for the new or target IMS subsystem, change the CSLG value (if used), to a new CSL suffix.
    4. Change the DBRCNM value to a new PROCLIB member.
    5. Change the DLINM value to a new PROCLIB member.
    6. Change PRDR value to a new PROCLIB member.
    7. If the new or target IMS subsystem will use a separate shared queue environment, change the SHAREDQ value to a new suffix.
    8. When the source IMS subsystem is connected to the Db2 or other external subsystems and if you want to clone these external subsystems without using IMS Cloning Tool, first create a PROCLIB member that defines connection to the external subsystems to be cloned and specify this member in the DFSPBxxx SSM= parameter.
  • When the source IMS subsystem is in an IMS-managed ACBs environment, create the same CATALOG section as in the source IMS subsystem to the member DFSDFxxx that specifies IMS components and processing options of functions. If the source IMS subsystem uses the IMS Catalog Definition exit routine (DFS3CDX0), the new DFS3CDX0 cannot be created in the source IMS.SDFSRESL before the cloning because the exit routine name is fixed as DFS3CDX0. Create the new DFS3CDX0 for the new IMS subsystem after the IMS subsystem is cloned.
Note: Additional information about configuring your IMS subsystem can be found in the IMS Installation Guide or IMS System Definition Guide.
If the associated optional IMS component is used, the following PROCLIB members must be created for the new IMS subsystem:
  • If IRLM is used, and if the new IMS subsystem uses a different IRLM than the source IMS subsystem:
    • A member to start the IRLM address space.
    • Also, the new IRLM subsystem ID must be defined to the z/OS® subsystem name table (IEFSSN)
  • If a DLI SAS is used:
    • A member to start the DLISAS address space.
  • If common service layer (CSL) address spaces are used and the new IMS subsystem uses a different CSL environment:
    • Members to start the CSL address spaces
    • A CSLOIxxx member to define OM options
    • A CSLRIxxx member to define RM options
    • A CSLSIxxx member to define SCI options
  • If shared queues are used and the new IMS subsystem uses a different shared queues address space than the source IMS subsystem:
    • A member to start the CQS address space. A DFSSQxxx member to define shared queue parameters.
  • If dynamic resource definitions are used:
    • A DFSDFxxx member to define DRD options and RDDS data sets
  • If external subsystem members are defined in the IMS subsystem to be cloned and if you want the new IMS subsystem to connect to the external subsystems:
    • A member to identify the external subsystem
Create new IMS.JOBS members for the new IMS subsystem. These members include:
  • JOBS to start any message processing regions.
  • JOBS to start any FP message processing regions.
  • SYSAFF member to indicate the z/OS system the new IMS subsystem runs on.