Control statements are input to the archival started task using the SARXCTAB DD statement and the following general structure:
/ID parameters
The slash is coded in column 1 and the job name immediately follows. One or more blanks follow the ID and separate it from the parameters. Separate individual parameters by one or more blanks, commas, or both. A statement that exceeds 71 characters is continued on additional statements. When continuing a statement, interrupt the statement only between complete parameters.
The ID identifies the job to which the statement applies. The statement is as follows:
jobname(.stepname(.procstepname))
Where
Specifies the name of the job to which the statement applies
You can specify a generic job name by appending an asterisk to the generic name. For example, a job name of PROD* specifies that the statement applies to any job having the first four characters of its name being PROD.
Specifies the name of the job step to which the statement applies
stepname is optional and can only be coded for completion code and/or abend exceptions. If omitted, the statement applies to all job steps.
Specifies the name of the procedure step to which the statement applies procstepname is optional and can only be coded for completion code and/or abend exceptions. If omitted, the statement applies to all procedure steps.
Because qualification by job and procedure step names only applies to completion code and abend exceptions, multiple control statements can be required for the same job. One statement specifies only the job name without further qualification.
|
Copyright © 2015 CA Technologies.
All rights reserved.
|
|