CA IDMS DLI Transparency Run-Time Environment › Batch Considerations › Modifying Existing DL/I Batch JCL

Modifying Existing DL/I Batch JCL

You can construct the JCL to execute the region controller by modifying the existing JCL for a DL/I batch application. If you do this, make sure you observe the following constraints.

Central Version Environment

• Change the program name to IDMSDLRC.
• Remove any statements that point to DL/I databases. Make sure that you point only to CA IDMS/DB load libraries, and not to IMS or DL/I load libraries.
• Insert a SYSCTL statement.
• Remove all DL/I database definitions.

In a Local Mode Environment

• Change the program name to IDMSDLRC.
• Remove any statements that point to DL/I databases. Make sure that you point only to CA IDMS/DB load libraries and not to IMS or DL/I load libraries.
• Do not include a SYSCTL statement.
• Replace all DL/I file definitions with CA IDMS/DB file definition cards.
• Add journal definition cards. Remember that local mode needs a larger address space than a job accessing the central version. This is because the local address space also includes CA IDMS/DB.

Using Dynamic File Allocation

• There are a number of advantages to utilizing FILE statements in the CA IDMS DMCL to have databases accessed using Dynamic Allocation.

  For more information about utilizing dynamic allocation, refer to the CA IDMS Database Administration Guide Volume 1, Chapter 3, Defining Segments, Files, and Areas.