The JCLs are built starting from CBDGLOD1 and CBDGLOD2 skeletons, which can be customized. The CBDUNLD2 skeleton is an alternative skeleton where the UNLOAD utility is used instead of the DSNTIAUL utility in order to create SYSPUNCHs.
The structure of the skeleton comprises a starting and ending part that are repeated once in the created JCLs, and a central part that is delimited by the following keywords:
|
//* SINGLE FILE ELABORATION and //* SINGLE FILE END ELABORATION, that is repeated for each file. |
In the skeleton some variables are used, and they are changed into the JCL values using the values stored in the Knowledge Base or included in the launch parameters.
The following table describes the used variables:
| Variable | Description |
|---|---|
| &NUM |
Numeric progressive |
| &UNLOUTNAM |
Name of the sequential data set (output of extraction process) |
| &OWNAME |
Owner of the original table |
| &FILNAME |
Name of the original table |
| &DBNAME |
Database name of the original table |
| &TSNAME |
Tablespace name of the original table |
| &UNLINPNAM |
Name of the unload as specified in the Work with files area |
| &STEP |
Step name for the SYSPUNCH generation (automatically generated) |
| &STP1 | Step name for the MISYSPUN program call (automatically generated) |
| &STP2 |
Name of the reload step (automatically generated) |
| &SYSPARM |
It can be ADD,YES, number of sortkeysif no replace parameter, REP,YES, number of sortkeysif replace parameter |
| &DSNNAME |
Name of the input DSN |
| &METHOD |
Name of the code |
| &JOBN |
Name of the job actualized with the JCL name |