Batch Considerations

idms
CA IDMS DLI Transparency batch can run in either a local mode or CV environment.
The following diagram shows the local mode environment.
IDMSDB--Batch Considerations
The following diagram shows the batch CV environment.
IDMSDB--Batch Considerations (2)
Steps to Set up Batch Environment
The steps for setting up the CA IDMS DLI Transparency batch environment (local mode or CV) are as follows:
  1. Link edit the DL/I applications with the CA IDMS DLI Transparency language interface.
  2. Execute the CA IDMS DLI Transparency region controller.
Link Editing Batch DL/I Applications
To prepare your DL/I applications to run in the CA IDMS DLI Transparency batch environment, you must link edit them with the correct CA IDMS DLI Transparency language interface.Module IDMSDLLI should be link edited to call-level DL/I applications, and module IDMSDLHI should be link edited to batch command - level DL/I applications (containing EXEC DLI commands).
To link edit a DL/I application program with the language interface, use the JCL for z/OS and z/VSE provided in section D.
Executing the CA IDMS DLI Transparency Region Controller
The Basic Execute Statement
To run CA IDMS DLI Transparency in a batch environment, you must execute the CA IDMS DLI Transparency region controller (IDMSDLRC). Use the JCL provided in section D.
The basic execute statement (shown for z/OS) is as follows:
EXEC  PGM=IDMSDLRC,PARM='DLI,userpgm,ipsb,parms'
Parameter List
In the PARM list:
  • Userpgm
    is the name of the DL/I batch application.
  • Ipsb
    is the name of the IPSB that the application uses when accessing the CA IDMS/DB database.
  • Parms
    are additional optional parameters, as follows:
    • TRACE
      -- Traces the call sequence, the I/O areas, the PCBs, and the SSAs. In a central version environment, the trace results are written to the CA IDMS/DB log. In a local mode environment, the trace results are placed in a special dataset called ESCDUMP. If you use TRACE when running in local mode, make sure that you include a DD statement for ESCDUMP. Generally, TRACE is used only for debugging internal problems.
    • NOSPIE/NOSTAE/NOSTXIT
      -- Prevents recursive abends in the case of CA IDMS DLI Transparency abend exit failures.The back-end module (RHDCDLBE) maintains a trace table of activity. If a DL/I application aborts, an abend exit is invoked to format and output the trace information to the CA IDMS/DB log in central version, or to the ESCDUMP DD in local mode. This information is valuable and used by support for diagnostic purposes. Under the central version, if the abend exit also abends, this recursive abend will bring the central version down. These parameters are available in case this situation should ever occur. This parameter should not be routinely specified.
      When running under the central version, only specify one of these options. NOSPIE and NOSTAE are for z/OS only. They turn off SPIES and STAES, respectively. NOSTXIT is for z/VSE only.
    • DYN
      -- Allocates dynamic buffers to the front-end module for use by PL/I programs. In order to use this parameter in a central version environment, you must make sure that the IPSB is available to both the region controller (IDMSDLRC) and the front-end module (IDMSDLFE), as well as to the back-end module (RHDCDLBE).
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 on utilizing dynamic allocation, refer to the
    CA IDMS Database Administration Section Volume 1
    , Section3, Defining Segments, Files, and Areas.