Previous Topic: Control StatementsNext Topic: JCL

Runtime Considerations › Loading Runtime Components

Loading Runtime Components

Order of Precedence

Runtime components (such as subschema load modules, dialog load modules, application definition blocks, and map load modules) can be stored in load areas and load libraries. The runtime system uses the following order of precedence when loading a component:

  1. Main memory of the batch region, in the event that the component has already been loaded
  2. The load area of the secondary dictionary, if any, specified in a control statement
  3. The load area of the system's primary dictionary
  4. A load library specified in the STEPLIB statement, if any

    Note: If an application snaps the application definition block (ADB) or fixed dialog block (FDB) of an application or dialog that was loaded from STEPLIB, only the header portion is snapped.

    An error status of 1474 may be returned if an CA ADS Batch program running in local mode attempts to use a subschema that was compiled for use on CA IDMS/DC without a DMCL name.

    CA ADS Batch can link to a user-written program. The program can perform database commands. The program, however, cannot perform QUEUE, WRITE PRINTER, or other DC/UCF-oriented commands.

    A user-written COBOL, or PL/I program accessed by an CA ADS Batch application must have been submitted to the DML preprocessor with a mode of BATCH.