Parameter field

An EXEC statement has two kinds of parameters: positional and keyword.

Do not use EXEC statement parameter keywords as symbolic parameters, names, or labels.

Positional Parameters: An EXEC statement must contain one of the positional parameters: PGM, PROC, or procedure name. This positional parameter must precede all keyword parameters.

Table 1. Positional parameters
POSITIONAL PARAMETERS	VALUES	PURPOSE
`PGM= {program-name } {.stepname.ddname } {.stepname.procstepname.ddname} {JCLTEST } {JSTTEST }` See section PGM parameter	program-name: 1 - 8 alphanumeric or $, #, @ characters member containing program stepname: DD in named step procstepname: step in named procedure JCLTEST and JSTTEST: scan for syntax without executing the job (JES3 only)	Names the program the system is to execute or, for JES3 only, requests syntax check without execution
`{PROC=procedure-name} {procedure-name }` See section PROC and procedure name parameters	procedure-name: 1 - 8 alphanumeric or $, #, @ characters	Names the cataloged or in-stream procedure the system is to call and execute.

Keyword parameters: An EXEC statement can contain the following keyword parameters. You can code any of the keyword parameters in any order in the parameter field after the positional parameter.

Table 2. Keyword parameters
KEYWORD PARAMETERS	VALUES	PURPOSE
`ACCT[.procstepname]=(accounting-information)` See section ACCT parameter	accounting-information: up to 142 characters [.procstepname]: name of procedure EXEC containing ACCT to be affected	Specifies accounting information for the step
`ADDRSPC[.procstepname]= {VIRT} {REAL}` See section ADDRSPC parameter	VIRT: virtual (pageable) storage REAL: central (nonpageable) storage [.procstepname]: name of procedure EXEC containing ADDRSPC to be affected	Indicates the type of storage required for the step.
`CCSID=nnnnn`	`nnnnn`: 1 - 65535	Specifies the coded character set identifier indicating the character code conversion performed on reads from and writes to tapes accessed in ISO/ANSI Version 4 format.
`COND[.procstepname]= ((code,operator[,stepname][.procstepname]) ) ([,(code,operator[,stepname][.procstepname])]...) ([,EVEN] ) ([,ONLY] )` See section COND parameter
	`code`: 0 - 4095 `operator: GT Code from GE chart on EQ section Table 1 LT LE NE` EVEN: execute step even if preceding step ended abnormally ONLY: execute step only if preceding step ended abnormally `stepname`: step issuing return code `procstepname`: step is in named procedure [.`procstepname`]: name of procedure EXEC containing COND to be affected	Specifies the return code tests used to determine if this step is to be executed or bypassed.
`DYNAMNBR[.procstepname]=n` See section DYNAMNBR parameter	n: 0 - 3273 minus number of DD statements in step [.procstepname]: name of procedure EXEC containing DYNAMNBR to be affected	Holds a number of data set allocations for reuse and sets the control limit.
`MEMLIMIT={nnnnnM} {nnnnnG} {nnnnnT} {nnnnnP} {NOLIMIT}` See section MEMLIMIT parameter	`n`: 0 - 99999	Specifies the limit on the total number of usable virtual pages above the bar in a single address space.
`PARM[.procstepname]=subparameter PARM[.procstepname]=(subparameter,subparameter) PARM[.procstepname]=('subparameter',subparameter) PARM[.procstepname]='subparameter,subparameter'` See section PARM parameter
	`subparameter`: up to 100 characters [.procstepname]: name of procedure EXEC containing PARM to be affected	Passes variable information to the processing program.
`PERFORM[.procstepname]=n` See section PERFORM parameter	n: 1 - 999 [.procstepname]: name of procedure EXEC containing PERFORM to be affected	In WLM compatibility mode (not available on z/OS® V1R3 or later systems), specifies the step’s performance group. In WLM goal mode, PERFORM on the EXEC statement is ignored except for the TSO logon procedure, where it can be used to classify the TSO user to a service class or report class.
`RD[.procstepname]= {R } {RNC} {NR } {NC }` See section RD parameter	R: restart, checkpoints allowed RNC: restart, no checkpoints NR: no restart, checkpoints allowed NC: no restart, no checkpoints [.procstepname]: name of procedure EXEC containing RD to be affected	In a non-APPC scheduling environment, indicates whether the operator should perform automatic step restart, if the step fails, and controls whether checkpoints are written for CHKPT macros or DD statement CHKPT parameters.
`REGION[.procstepname]={valueK} {valueM}` See section REGION parameter	valueK: 1 - 7 digits from 1 - 2096128 valueM: 1 - 4 digits from 1 - 2047 [.procstepname]: name of procedure EXEC containing REGION to be affected	Specifies the amount of space in kilobytes or megabytes required by the step.
`RLSTMOUT[.procstepname]={nnn} {0 }`	`nnn`: a value in seconds ranging from 0 to 9999. 0: this value means that the request has no time out value.	Specifies the maximum time in seconds that a VSAM RLS or DFSMStvs request is to wait for a required lock before the request is assumed to be in deadlock.
`TIME[.procstepname]= {([minutes][,seconds])} {1440 } {NOLIMIT } {MAXIMUM }` See section TIME parameter	minutes: 1 - 357912 seconds: 1 - 59 [.procstepname]: name of procedure EXEC containing TIME to be affected NOLIMIT: specifies that the step can use the processor for an unlimited amount of time MAXIMUM: specifies that the step can use the processor for the maximum amount of time	Specifies the maximum time the step is to use the processor and requests messages giving the time used.

Keyword parameters on an EXEC statement that calls a procedure: When an EXEC statement positional parameter calls a cataloged or in-stream procedure, all of the EXEC statement’s keyword parameters override matching EXEC keyword parameters in the called procedure. If a keyword parameter is to override a parameter on only one EXEC statement in the procedure, code .procstepname immediately following the keyword:

   keyword.procstepname=value

The procstepname is the name field on the procedure EXEC statement containing the keyword parameter to be overridden. For example:

   //STEP1  EXEC  PROC=WKREPORT,ACCT.PSTEPWED=5670

The accounting information 5670 applies only to step PSTEPWED in the procedure WKREPORT.

Symbolic parameters on an EXEC statement that calls procedures: An EXEC statement can assign values to, or nullify, symbolic parameters. See Using system symbols and JCL symbols for more information about symbolic parameters.