z/OS JES2 Initialization and Tuning Reference
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


Parameter description for JOBDEF

z/OS JES2 Initialization and Tuning Reference
SA32-0992-00

ACCTFLD=IGNORE|REQUIRED|OPTIONAL
Specifies whether the JES2 form of the accounting information (the job accounting number and room number) is required (REQUIRED), ignored by JES2 if present (IGNORE), or is not required but used by JES2 if present (OPTIONAL) on the JCL JOB statement for this job.

If ACCTFLD=REQUIRED is coded, JES2 cancels your job when either of the accounting field parameters is missing and issues message $HASP110 jobid jobname ILLEGAL JOB CARD.

Modification: $T JOBDEF operator command.

BAD_JOBNAME_CHAR=c|?
Specifies the character to use in place of invalid characters in a jobname. This translation is used for JES2 commands and displays RACF® entity names too. Valid values are: A-Z,0-9, $, #, @, /, +, :, ?, _, -, !

Modification: $T JOBDEF operator command or JES2 cold start

Start of changeCISUB_PER_AS=nn|5End of change
Start of changeSpecifies the nn number of converter/interpreter subtasks (1-25) that are run in each of the jesxCIxx address spaces when INTERPRET=JES is specified. Valid values are 1-25 (25 being the maximum number of converter PCEs that can be specified on PCEDEF).

Modification: $T JOBDEF operator command

End of change
CNVT_ENQ=WAIT|FAIL
Specifies how the system should process jobs that request JCLLIB data sets that are already enqueued at job conversion time.
WAIT
Indicates that system will allow the job to wait for the enqueued data set.
FAIL
Indicates that the system will fail (with a JCL error) a job that requests an unavailable JCLLIB data set.

Modification: $T JOBDEF operator command or cold start. Note that this parameter cannot be modified through a hot start, quick start, or single-member warm start, such that the parameter value in effect before the termination will be used.

Start of changeCNVT_SCHENV=HONOR|IGNOREEnd of change
Start of changeSpecifies whether the availability of a scheduling environment that is associated with a job controls which member a job converts on. If CNVT_SCHENV=HONOR is specified, then a job can only convert on a system where the scheduling environment associated with the job is available.

Modification: $T JOBDEF operator command. This parameter cannot be modified by a hot start, quick start or single-member warm start.

End of change
DUPL_JOB=NODELAY|DELAY
Specifies whether or not JES2 is allowed to concurrently execute batch jobs with the same name in the same MAS.
DELAY
Do not allow JES2 to execute batch jobs with the same name in the same MAS at the same time.
NODELAY
Allow JES2 to execute batch jobs with the same name in the same MAS at the same time.

Modification: $T JOBDEF operator command or JES2 cold start.

CNVT_ENQ=WAIT|FAIL
Specifies how the system should process jobs that request JCLLIB data sets that are already enqueued at job conversion time.
WAIT
Indicates that system will allow the job to wait for the enqueued data set.
FAIL
Indicates that the system will fail (with a JCL error) a job that requests an unavailable JCLLIB data set.

Modification: $T JOBDEF operator command or cold start. Note that this parameter cannot be modified through a hot start, quick start, or single-member warm start, such that the parameter value in effect before the termination will be used.

Start of changeDEF_CLASS=class|AEnd of change
Start of changeSpecifies a default class that JES2 will use if a non-valid class is discovered during processing. The specified class must be a defined and active batch job class. The specified class cannot be set to ACTIVE=NO, and cannot be deleted. The following examples show when the default class would be used:
  • When a job is submitted with a CLASS= value that is not valid. The job is failed, but this class is associated with the job for later processing.
  • When a job class is deleted that is associated with the INTRDR statement as CLASS=. The INTRDR CLASS value is set to this value.
  • During initialization processing, when the CLASS= value that is specified for a reader (INTRDR, local or remote) is not valid and the operator continues initialization.
The default is A.

Modification: $T JOBDEF operator command or a JES2 all-member warm start.

Scope: MAS-wide

End of change
Start of changeINTERPRET=INIT|JESEnd of change
Start of changeSpecifies when JES2 calls the MVS interpreter to process a job. The INTERPRET parameter is only valid when JES2 is in z11 mode. The INTERPRET parameter is not supported in z2 mode.
INIT
Specifies to call the interpreter when the job is selected for execution by an initiator. Invoking the interpreter in the initiator is the traditional JES2 processing method.
JES
Specifies for JES2 to call the interpreter at the end of conversion processing. The following functions are available if processing is done under JES (after conversion):
  • Earlier detection of JCL errors that are detected by the MVS interpreter. This allows errors to be detected even if the job never executes for TYPRUN=.
  • Processing of JESDS OUTPUT statements to control data set attributes, even if the job never executes.
Note: Specifying INTERPRET=JES causes EXIT 60 to be driven instead of exit 6. If you use exit 6, you might need to also provide similar function in exit 60 before setting interpret=JES.

Modification: $T JOBDEF operator command.

End of change
JNUMWARN=nnn|80
Specifies the percentage (1–99) of assignable job numbers (specified through the RANGE= parameter) that have been used for jobs submitted at the local node at which the operator is to be alerted with message $HASP050 JES2 RESOURCE SHORTAGE.

Modification: $T JOBDEF operator command. Note that this parameter cannot be modified through a hot start, quick start, or single-member warm start.

JOBNUM=nnnnn|1000
Specifies the maximum number (must be no greater than 400000) of jobs that can be in the JES2 job queue at any given time. This value includes all TSU, STC jobs, and batch jobs.

Performance Consideration: Specify JOBNUM= large enough to accommodate all jobs (including batch jobs, started tasks, and TSO/E logons) in the system at all phases of processing. Be careful not to specify a value that is too small.

If you use the $T JOBDEF command to increase JOBNUM=, only do so when you can allow your system to experience temporary performance degradation while all JES2 systems read the checkpoint data set.

Note: Start of changeUse this parameter to increase the limit for the JNUM resource that is reported on the HASP050 message.End of change

Modification: $T JOBDEF operator command to increase or decrease the number of jobs.

JOBWARN=nnn|80
Specifies the percent (1–99) usage threshold of available job queue elements (JQEs) at which the operator is to be alerted with message $HASP050 JES2 RESOURCE SHORTAGE. If you specify 0, no alert will be given.

Modification: $T JOBDEF operator command. Note that this parameter cannot be modified through a hot start, quick start, or single-member warm start.

Start of changeLOGMSG=ASIS|FOLDEnd of change
Start of changeSpecifies whether the messages issued by JES2 and written at job JCL converter time are mixed-case (ASIS) or uppercase (FOLD). The default is ASIS.

Modification: $T JOBDEF operator command or JES2 start.

End of change
PRTYHIGH=nn|10
Specifies the upper priority limit (0-15) to be associated with the JES2 job priority-aging feature. A job will not be priority-aged if its priority is (or becomes) greater than or equal to the value specified in this parameter. Jobs on the $HARDCPY queue are not priority aged.

Modification: $T JOBDEF operator command. Note that this parameter cannot be modified through a hot start, quick start, or single-member warm start.

PRTYJECL=YES|NO
Specifies whether the JES2 /*PRIORITY control statement is to be supported (YES) or ignored (NO).

Modification: $T JOBDEF operator command.

PRTYJOB=YES|NO
Specifies whether the priority specified (PRTY= keyword) on the JCL JOB statement is supported (YES) or ignored (NO).

Modification: $T JOBDEF operator command.

PRTYLOW=nn|5
Specifies the lower priority limit (0-15) to be associated with the JES2 job priority-aging feature. A job will not be priority-aged unless its priority is initially equal to or greater than this value. Jobs on the $HARDCPY queue are not priority aged. (See the PRTYRATE= and PRTYHIGH= parameters on this initialization statement for additional information.)

Modification: $T JOBDEF operator command. Note that this parameter cannot be modified through a hot start, quick start, or single-member warm start.

PRTYRATE=nnnn|0
Specifies the number (0-1440) of time periods into which a 24-hour day is to be divided for use in increasing a job's priority by the JES2 priority-aging feature. For example, if 3 is specified, a job's priority will be increased by one for every 8 hours it remains in the system. However, a job's priority will not be incremented unless it is at least equal to the value specified in the PRTYLOW= parameter; nor will a job's priority be increased above the value specified in the PRTYHIGH= parameter. If 0 is specified, the values specified in the PRTYLOW= and PRTYHIGH= parameters are ignored. See z/OS JES2 Initialization and Tuning Guide for a discussion of this processing.

If a job's priority is specified on a /*PRIORITY control statement or through the PRTY parameters on the JOB card, the job will be priority-aged if its priority is eligible. See the JOBPRTY statement (JOBPRTY= parameter) and OUTPRTY statement (RECORD=, PAGE=, and PRIORITY= parameters) in this chapter for additional information.) Jobs in WLM-mode job classes are not priority aged.

Modification: $T JOBDEF operator command. Note that this parameter cannot be modified through a hot start, quick start, or single-member warm start.

RANGE=nnnnn[,mmmmm]|1,9999
Specifies the range of numbers (1 through 999999) which JES2 will assign as JOBIDs to jobs which originated on the local node.

The integer n specifies the lowest number (1 through 999999) which will be assigned as a JES2 job identifier for jobs originating locally.

The integer m specifies the highest number (n+10 through 999999) which will be assigned as a JES2 job identifier to jobs originating locally. Note that setting the upper limit above 99,999 will cause the JOBID format to change from CCCNNNNN to C0NNNNNN where CCC is either JOB, STC, or TSU, and C is J, S, or T. NNNNN or NNNNNN is a number.

Note: Start of changeUse this parameter to increase the limit for the JNUM resource that is reported on the HASP050 message.End of change

Modification: $T JOBDEF operator command or cold start. If you modify this parameter and then restart JES2 with a warm or hot start, the parameter value in effect before the termination will be used.

RASSIGN=No|Yes
Specifies whether job numbers outside of the RANGE definition can be assigned to jobs received through NJE or spool reload. YES= Jobs with original job numbers outside JOBDEF RANGE will retain their original job number, if possible. NO= Jobs with original job numbers outside JOBDEF RANGE will always be assigned a new job number within the range.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014