Using supplied variables
The example using SYSTEM needs some manual intervention when the value of the SYSTEM variable must be changed (either at a setup workstation or using the variable table panel). But you can use dependent variables even in a fully automatic system, if the independent variable is a supplied variable.
This example shows how to change variables automatically, depending on the input arrival day of the occurrence. The supplied variable is ODAY, which has values from 1 (Monday) to 7.
This is how the dependent variable (HLQ1) is defined:
EQQJVVMP ----------------- MODIFYING A JCL VARIABLE --------------------- Command ===> Enter/Change data below, or DEP command to create/modify dependency, enter VER command to define verification rules. Variable table : SPECIALONMONDAY Variable name : HLQ1 DESCRIPTION ===> high-level-qualifier Descriptive text DEFAULT VALUE ===> OTHER.DAYS__________________________________ UPPER CASE ===> Y Y - Yes, N - No SETUP ===> Y Y - Yes, N - No, P - Prompt SUBSTITUTION EXIT ===> ________ A load module name VALUE REQUIRED ===> Y Y - Yes, N - No
The default value, OTHER.DAYS, is used when there is no match on the independent variable values.
EQQJVDVL ------------ JCL VARIABLE DEPENDENCY VALUE LIST ---- ROW 1 TO 1 OF 1 Command ===> Scroll ===> PAGE Enter any of the row commands below: I(nn) - Insert, R(nn), RR(nn) - Repeat, D(nn) - Delete Enter DEL command to delete this dependency. Dependent variable : HLQ1 high-level-qualifier Variable table : SPECIALONMONDAY Default value : OTHER.DAYS INDEPENDENT VARIABLE ===> ODAY Row cmd '' VALUE OF INDEPENDENT ===> 1 VALUE OF DEPENDENT ===> DAY1
HCL Workload Automation for Z substitutes DAY1 for the HLQ1 variable when ODAY=1. On other days, it uses the default value OTHER.DAYS. ODAY is a setup or submit variable, so HLQ1 can also be specified as a setup or submit variable.