Function

To specify the job processing characteristics of JES2.

Parameters

ACCTFLD={IGNORE|OPTIONAL|REQUIRED}

Specifies the type of scan that JES2 is to perform on the JCL JOB statement account field:

IGNORE

If the account field is specified on the JOB statement, it is ignored.

OPTIONAL

The account field on the JOB statement is optional and no account parameters are required.

REQUIRED

The account field is required on the JOB statement and the first two positional parameters must be specified.

Note: The specified value is applied only to those jobs that have not yet entered the system.

Scope: Single Member.

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 as well as RACF® entity names. Valid values are: A-Z, 0-9, $, #, @, /, +, :, ?, _, -, !

Scope: MAS-Wide.

CISUB_PER_AS=nn

Specifies the nn number of subtasks (converter/interpreter subtasks) 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).

CNVT_ENQ={FAIL|WAIT}

Specifies if the converter should WAIT for the unavailable data set to become available or FAIL (with a JCL error) a job that requests an unavailable JCLLIB data set.

Scope: MAS-Wide

CNVT_SCHENV=HONOR|IGNORE

Specifies 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.

DEF_CLASS=class|A

Specifies 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 class value is A.

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

Scope: MAS-wide

DUPL_JOB={DELAY|NODELAY}

Specifies whether 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 to execute at the same time.

Scope: MAS-Wide.

INTERPRET=JES|INIT

Specifies when JES2 calls the z/OS interpreter to process a job. INIT specifies that the interpreter is called when the job is selected for execution by an initiator.

Note: The INTERPRET parameter is only valid when JES2 is in z11 mode. The INTERPRET parameter is not supported in z2 mode.

JES specifies that it will be called by JES2 at the end of conversion processing. When INTERPRET=JES is specified, conversion and interpretation processing occurs in a subtask in a new address space named jesxCIxx. Invoking the interpreter in the initiator is the traditional way that JES2 processing works. However, the following functions are available if processing is done under JES (after conversion):

• Earlier detection of JCL errors detected by the z/OS interpreter. This allows errors to be detected even if the job never executes for TYPRUN=.
• Processing of JESDS OUTPUT statements to control the attributes of JES data sets, even if the job never executes.

JOBNUM=nnnnnn

Specifies the maximum number (10-400000) of jobs that can be in the JES2 job queue at any given time. This value includes all TSU and STC jobs, as well as batch jobs. This number can be increased or decreased by operator command. If JOBNUM is increased, JES2 may assign a larger value to BERTNUM to reduce the chance of a shortage of BERTs. However, installations should monitor BERT usage (using $D CKPTSPACE,BERTUSE and the $HASP050 message) to ensure they do not run out of BERTs.

JNUMWARN=nnn

The percentage (1-99) of assignable job numbers (for jobs originating at the local node) used at which the $HASP050 message alerts the operator of a shortage of job numbers. JES2 deletes this message from the console when the shortage is relieved (either by a decrease in resource use or by an increase in the threshold).

Scope: MAS-Wide.

JOBWARN=nnn

The percentage (0-100) of job queue elements used at which the $HASP050 message alerts the operator of a shortage of job queue elements. JES2 deletes this message from the console when the resource shortage is relieved (either by a decrease in resource use or an increase in the threshold).

Note: If you specify 0, no alert is given.

Scope: MAS-Wide.

LOGMSG={ASIS|FOLD}

Specifies whether the messages issued by JES2 and written at job JCL converter time are mixed-case (ASIS) or uppercase (FOLD). The default is mixed-case (ASIS).

Scope: MAS-Wide.

PRTYHIGH=nn

The upper priority limit (0-15) associated with the JES2 job priority aging feature. JES2 does not priority-age a job if the job's priority is (or becomes) equal to, or greater than, the PRTYHIGH value.

Note: The specified value is applied only to those jobs that have not yet entered execution.

Scope: MAS-Wide.

PRTYJECL={No|Yes}

Specifies whether the priority specification on the JES2 /*PRIORITY control statement is to be supported or ignored.

Note: The specified value is applied only to those jobs that have not yet entered the system.

Scope: Single Member.

PRTYJOB={No|Yes}

Specifies whether the priority specification (PRTY=) on the JOB statement is to be supported or ignored.

Note: The specified value is applied only to those jobs that have not yet entered execution.

Scope: Single Member.

PRTYLOW=nn

The lower priority limit (0-15) associated with the JES2 job priority aging feature. JES2 does priority-age a job only if the job's priority is initially equal to or greater than the PRTYLOW value.

Note: The specified value is applied only to those jobs that have not yet entered execution.

Scope: MAS-Wide.

PRTYRATE=nnnn

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. JES2 uses this rate to increase the job's execution priority and the job's output priority. For example, if you specify PRTYRATE=3, JES2 increases a job's priority by one for every 8 hours it remains in the system.

Note:

1. The specified value is applied only to those jobs that have not yet entered execution.
2. JES2 increases a job's priority only if it is equal to or above the value specified by the PRTYLOW parameter.
3. JES2 does not increase a job's priority above the value specified by the PRTYHIGH parameter.
4. If you specify zero, no priority aging is performed.
5. Jobs in WLM-node job classes are not priority aged.

Scope: MAS-Wide.

RANGE=(nnnnnn,mmmmmm)

The range of job numbers (1-999999) that JES2 uses to assign JOBIDs to jobs originating on the local node.

nnnnnn

The lowest number (1-999989) that is assigned as a JES2 job identifier for jobs originating at the local node.

mmmmmm

The highest number ((nnnn+10)-999999) that is assigned as a JES2 job identifier for jobs originating at the local node. The value specified for the highest number (mmmmmm) must be equal to the lowest number (nnnnnn) or at least 10 greater than the value used for the lowest number (nnnnnn).

If you code this parameter, you can specify one or two values:

• If you specify one value, that value becomes both the low and the high end of the range.
• If you specify two values, the first value is the low end of the range and the second value the high end. The two values can be equal. If they are not equal, the second value must be larger than the first value.

Note:

1. The specified value is applied only to those jobs that have not yet entered the system.
2. JES2 maintains the new RANGE= specification until you perform a cold start or issue another $T JOBDEF,RANGE=( ) command.
3. Setting JOBDEF RANGE upper limit above 99,999 will cause the jobid format to change from CCCNNNNN to C0NNNNNN where CCC is JOB/STC/TSU and C is J/S/T and NNNNN and NNNNNN are numbers.

Scope: MAS-Wide.

RASSIGN={No|Yes}

Specifies whether job numbers outside of the RANGE definition can be assigned to jobs received through NJE or spool reload.

Scope: Single Member.

Processing Considerations

See the individual parameter descriptions to determine the impact of this command on jobs in different phases of execution.

Scope

The scope of this command varies by parameter. See the description of each parameter for its scope.

The values supplied for some parameters on this command will be in effect across the entire MAS, while the values supplied for other parameters will be in effect for this member only.

Depending on your installation's setup, you might want the single-member parameters for this command to be applied to all members of the MAS (to ensure a consistent environment across the MAS). If so, you can use the MVS™ ROUTE *ALL command to issue this command to all active members (if the JES2 command character is the same on all members). See z/OS MVS System Commands, SA38-0666 for more information on using the ROUTE *ALL command.

Messages

The $HASP835 message displays the current values of all the parameters on the JOBDEF initialization statement.

JES2 supports the priority specification on the JCL JOB statement. JES2 priority-ages all jobs whose initial priority is equal to, or greater than, 3 and less than 12. If a job's priority becomes 12, JES2 stops priority-aging that job.