Utilities › RMOJCL - Automatic Database Construction From JCL › Job Control Statements

Job Control Statements

Specify the following JCL to execute RMOJCL:

JOB

Initiates the job.

EXEC

Specifies the program name (PGM=RMOJCL) and, optionally, the high-level name of the database as the PARM parameter (PARM='DELIVER.SYSTEM1').

STEPLIB DD

Identifies the load library that contains RMOJCL.

If the program resides in a linklist library, you can omit this statement.

SYSPRINT DD

Identifies the sequential output data set (typically the SYSOUT) to which control statements and messages are to be sent.

If you do not specify a SYSOUT data set, specify DCB=BLKSIZE=nnn, where nnn represents a number that is a multiple of 133.

JOBJCL DD

Defines the sequential or partitioned data set containing the JCL for the jobs to be input.

For a sequential data set, the jobs is stacked together; for a partitioned data set, each member contains one job with the member name equal to the name of the job. In both cases, the actual job name used is the one contained on the JCL JOB statement.

PROCLIB DD

Defines the cataloged procedure libraries.

Multiple libraries can be specified by concatenating the DD statements for the libraries. Be sure to specify all the libraries that can be required. The procedure libraries in use at your installation can be determined by examining the JCL procedure in SYS1.PROCLIB for starting JES2 or JES3.

SYSIN DD

Specifies the name of the card image data set where the control statements you want to input are located.

• The keyword TEST can be coded as the second subparameter of the PARM field on the EXEC statement to indicate that a test run of the utility is to be made (for example, PARM='DELIVER.SYSTEM1,TEST'). A test run scans the JCL and produces a detailed report of the SYSOUT DD statements. No data, however, is added to the database.
• The keyword CHECK can be coded as the second subparameter of the PARM field on the EXEC statement (for example, PARM='DELIVER.SYSTEM1,CHECK') to compare job definitions in the database to the production JCL.

Note: An RMOJCL control statement must fit entirely on one card image. Continuations are not allowed.