|
|
|
|
|
A major advantage of using AutoEdit variables is that the JCL can be submitted with different values for different executions without actually changing the JCL.
There are two types of AutoEdit variables:
One method of supplying a value for a user-defined variable is by defining the variable and its value in a DO SET statement.
During job processing, the value is assigned at time of job submission. However, DO SET is a post-processing statement, which means that before it can be applied, its accompanying ON criteria must be satisfied in a job run.
Therefore, the DO SET statement is generally useful for supplying local user-defined variables for cyclic, rerun, or restarted jobs.
When the ON criteria of a DO SET statement that defines a local variable are satisfied during a job run, Control-M creates a SET VAR statement equivalent to the DO SET statement (that is, containing the same variable and value) in the subsequent job run.
At time of job submission, AutoEdit variables in the JCL are resolved in the order in which they appear in the JCL. By default, if an AutoEdit variable cannot be resolved, the job is not submitted. This default can be changed using an appropriate %%RESOLVE AutoEdit control statement.
Note: If the JCL contains an AutoEdit variable that is resolved in a subsequent run by a DO SET statement, the variable must be resolved by some other method, such as a SET VAR statement, in the original run, or the job is not submitted.
DO SET statements can also be used to define and update Global Variables in the IOA Global Variable database. The database is updated as part of job post-processing, when the DO SET statement is processed. For more information on Global Variables, including Global Variable syntax, see JCL and AutoEdit Facility.
An unlimited number of DO SET statements can be specified.
JCL Setup and the AutoEdit facility are described in depth in JCL and AutoEdit Facility.
Parent Topic |