JCL installation

The BVPMMJCL module reads the skeleton JCL file and produces an appropriate JCL, with commands that you can use to do the following actions:

This step can be run as many times as necessary to generate an appropriate JCL.

This step includes the following user input.
Commands Parameters Comments
===PRM PPPP=pppp (PPPP is the parameter name and pppp is the parameter value) Parameter
===SELM JCL1 JCL2 ....... Selected JCL modules
===BEGMOD Insertion of lines at the beginning of module
....1   Lines to be added before each module
....n    
===ENDMOD   Insertion of lines at the end of module
....1   Lines to be added after each module
....n    

Notes on the user input:

The result is the creation of the complete JCL.

The file obtained in SYSUT2 contains all the installation and operation JCLs. This file must be open with an editor to launch the installation process.

Two operations must be completed on the complete JCL.

1. Overall modifications (if necessary)

All the JCLs can be adapted.

The VSAM catalogs appear as comments in the JCL obtained after the installation on the following lines:

When these parameters are not required on the site, the resulting JCL can remain as is.

When these parameters are required on the site, the relevant lines should be changed into command lines. To do so, you must transform all '//*:' into '//'. Then, replace '/*:' and '*/' with blanks.

2. JCL splitting

Before each module of a standard complete JCL, there is a ./ ADD NAME=<JCL-module> line, where <JCL-module> is the code of the ===MOD line found (see the following table of JCL modules).

The complete JCL can then be split into as many members as JCL modules in a PDS. The complete JCL file is to be used as SYSIN in the PDS update utility: IEBUPDTE.

Because of this default option, all './' characters found in JCL modules containing IEBUPDTE were replaced with ':/'.

When the JCL is split, the replacement must be performed the other way round before the jobs that contain IEBUPDTE can be run.

OUTPUT REPORT

BVPMMJCL produces a list for each JCL module created, with the parameters and according to the variants requested.

Since the parameters of the skeleton JCL are formatted as $xxxx, if BVPMMJCL encounters, upon execution, a $ character that does not correspond to a defined parameter, it sends error messages such as: 'Unknown symbolic parameter' or 'Invalid position or length' or 'Syntax error in symbolic parameter'.

These messages do not stop the execution and should be ignored: they apply to '$' characters present in the flow processed by BVPMMJCL but which are not parameters.


Feedback