Using the JCL script language

This section describes the JCL script language that you can use with BMC database administration products for IMS. BMC provides a JCL scripting language that you can use to write custom solution scripts for your environment.

Scripts are instructions that are executed when a user generates and submits JCL with the Generate JCL function. Using the JCL script language, you can create scripts that meet the specific requirements of your environment.

The JCL scripts that BMC distributes with the database administration products for IMS are stored as follows:

  • The predefined script load modules are stored in the SCRIPTLB data set. The default target data set name is hlq.DBUSCRL (if the non-merged option is selected during installation) or hlq.IMSCRL (if the merged option is selected during installation).
  • The script source code is stored in the SCRIPTSC data set. The default target data set name is hlq.DBUSCRS (if the non-merged option is selected during installation) or hlq.IMSCRS (if the merged option is selected during installation).

Both data sets are specified in the CPCxINI initialization file (which is located in the sample library). The ddname that defines the SCRIPTLB data set is UTIDSN. The ddname that defines the SCRIPTSC data set is USERDSN.

During installation, both data sets are allocated and populated. You can add scripts to the SCRIPTSC data set. No restrictions apply to the number or size of JCL scripts.

At execution, source scripts are interpreted dynamically. Interpreted script listings containing syntax messages and instruction numbers are written to the SYSOUT file. If a script contains invalid syntax, processing terminates with errors; review the output file for error messages.

The following SYSOUT-type files are produced in the ADV server address space if the corresponding DD statements have been added to the ADV procedure (PROC):

  • The DUELIST data set is written when a script source is used and contains interpreted script listings, including syntax messages and instruction numbers.
  • The DUEPRINT data set is written when a script is executed.
  • The DUETRACE data set is written when you turn on tracing in the INI file.

Scripts are located for execution in the following order:

  1. Load library of scripts (SCRIPTLB)
  2. Source library (SCRIPTSC)

This section contains the following topics:


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*