Parameters

ALTJCL=

Specifies whether JES3 recognizes JES3 control statements in JCL that begin with "/*" instead of "//*" (for example, /*MAIN instead of //*MAIN).

ERROR - indicates that JES3 control statements beginning with "/*" will be rejected, and will cause the job to be canceled with an error message.
IGNOREW - indicates that JES3 control statements beginning with "/*" will be rejected, and will cause a warning message to be issued, but will not cause the job to be canceled.
COMMENT - indicates that JES3 control statements beginning with "/*" will be rejected. No messages will be issued.
ACCEPT - indicates that certain JES3 control statements beginning with "/*" will be processed. Note that some JES3 control statements, such as //*NET, must begin with "//*". These will be treated as comments. This is the default.

CARDS=

Defines the maximum number of cards a job may punch and how to handle jobs exceeding this maximum.

nnn

Specifies the maximum number of cards, in hundreds, from 1 to 999. The default is 2; that is, 200 punched cards.

CANCEL or C

Specifies that a job be canceled without a dump if it exceeds nnn.

DUMP or D

Specifies that a job be canceled with a system abend dump if the job exceeds nnn.

WARNING or W

Specifies that JES3 issue a warning message and continue processing the job if it exceeds the punch limit. JES3 reissues a warning message for every additional 100 (default) cards the job punches.

mmm or 50: Regulates the frequency that JES3 issues message IAT1600 after exceeding the maximum punch limit (mmm is a percentage of the maximum punch limit). The value you specify must be a multiple of 10 between 10 and 100 inclusive. Specifying too low a value can cause JES3 to flood the system with messages which in turn, can cause a shortage of staging areas and console buffers. To decrease the number of messages issued, use higher values for nnn and mmm.

If you specify an invalid subparameter, JES3 uses the parameter default.

CIBATCH=

Indicates whether batch jobs must have CI processing limited to certain processors. This will apply to all batch jobs unless overridden by the CIBATCH parameter on the CLASS statement pertaining to a job's JOB CLASS.

JOB - indicates CI processing must be performed on a system on which the job is eligible to run.
Note: Either the SYSTEM or SYSAFF parameter on the JOB control statement, or the SYSTEM parameter on the //*MAIN control statement, are considered for CI scheduling purposes when determining where the job is eligible to run. The job's scheduling environment does not apply.
CLASS - indicates CI processing must be performed on a system on which the job's JOB CLASS is enabled.
ANY - indicates CI processing may be performed on any processor regardless of job or class eligibility. This is the default.

CIDEMAND=

Indicates whether demand select jobs must have CI processing limited to certain processors. This will apply to all demand select jobs unless overridden by the CIDEMAND parameter on the CLASS statement pertaining to a job's JOB CLASS.

JOB - indicates CI processing must be performed on a system on which the job is eligible to run.
CLASS - indicates CI processing must be performed on a system on which the job's JOB CLASS is enabled.
ANY - indicates CI processing may be performed on any processor regardless of job or class eligibility. This is the default.

CICNT=

Specifies the maximum number of CI DSPs that can operate in the JES3 global address space at any time. The first subparameter (maxbatch) specifies the maximum number of CI DSPs that process batch jobs. The second subparameter (maxdemsel) specifies the maximum number of CI DSPs that process demand select jobs (that is, started tasks and TSO LOGONs).

The sum of the two subparameters cannot exceed 255. CI DSPs defined to process batch jobs cannot be used to process demand select jobs, and vice versa.

Specify as small a number as practical, since this parameter can be modified using an operator command. The count can be incremented or decremented using the *MODIFY,X operator command.

Note:

If you specify CICNT=(0,0), no CI DSPs will run in the JES3 global address space. However, specifying CICNT=0 defaults to CICNT=(0,1) and results in one demand select CI DSP in the JES3 global address space.
If you define C/I FSS address spaces for your installation, JES3 creates a special C/I subtask in the JES3 global address space for starting C/I FSS address spaces; it cannot be used for starting other tasks or TSO LOGONs. This subtask allows a C/I FSS address space to be started even if you specify CICNT=(0,0) in the initialization stream.

If you specify an invalid subparameter, JES3 uses the parameter default.

PSTCNT=

Specifies the maximum number of POSTSCAN DSPs that can operate in the JES3 global address space at any one time. The first subparameter (maxbatch) indicates the maximum number of POSTSCAN DSPs that can process batch jobs. The second subparameter (maxdemsel) indicates the maximum number of POSTSCAN DSPs that process demand select jobs (that is, started tasks and TSO LOGONs). A POSTSCAN DSP defined as processing batch jobs cannot be used to process demand select jobs, and vice versa.

The total of both numbers specified for this parameter must be between 1 and 32,767 (inclusive).

For guidelines on choosing a value for this parameter, see “Configuring C/I Processing” in z/OS JES3 Initialization and Tuning Guide.

Parameter Default: The combined maximum number of CI DSPs in the JES3 complex that can process batch jobs (maxbatch) and demand select jobs (maxdemsel). (That is, the total number of CI DSPs specified on the CICNT parameter of the STANDARDS statement, plus the number of CI DSPs specified on the DSPCNT parameter of every FSSDEF statement for a C/I FSS address space, including all values allowed to default.)

DBGCLASS=

Specifies the default message class for the debug data set written by the debug facility and the default SYSOUT class for JES3 Dynamic Support Programs (DSP).

FAILURE=

Specifies the default job recovery option to be applied to jobs active at the time of a main restart failure. This parameter is used if the FAILURE option is not indicated on the CLASS statement associated with the job and the job does not have a main MVS™ checkpoint/restart option specified in its JCL.

CANCEL: Specifies that the job be canceled on the main.
HOLD: Specifies that the job be held for restart on the main.
PRINT: Specifies that the job be printed and held for restart on the main.
RESTART: Specifies that the job be restarted on the main at the beginning of the first step.
Note: If a job has been registered as an element of automatic restart management, the FAILURE= keyword is ignored.

If automatic restart management decides to start the job, all non-spin sysout data sets created during the previous execution will be deleted.

A job in a JES3 system can have a failure option specified in one of the following:

//*MAIN JECL statement in the job's JCL
CLASS statement in the JES3 initialization stream
STANDARDS statement in the JES3 initialization stream

Note: Higher items override lower items in the above list.

The failure option is used to determine the disposition of a job when one of the following occurs:

The job is executing and the processor on which the job is executing fails (is IPLed).
The job terminates abnormally.
The job goes through end of memory.
A *RESTART,main,jobname/jobno command has been issued for a job that is already running and the job is not registered with Automatic Restart Manager (ARM). If the failure option is RESTART, the job will be restarted. If the failure option is CANCEL, the *RESTART,main,jobname/jobno command is not accepted, and the job continues to run. If the failure option is HOLD, the job is canceled, and then placed in operator hold. If the failure option is PRINT, the job is printed, then it is placed in operator hold.
A *START,mainname,FLUSH command was issued for a local processor and there were jobs running on the specified local.
A *MODIFY Q,DD=ddn,STOP command was issued for a spool data set. This command holds the specified spool data set and suspends further scheduling for all jobs that have data on the data set, if the jobs are not currently active on a processor. But, if there were a job that had data on the data set, and it was active on main, JES3 issues a command to MVS on the appropriate processor to (MVS) cancel the job. All jobs (whether active on main or not) get placed into spool hold status. Later, if a *MODIFY Q,DD=ddn,RELEASE command is issued to release the specified spool data set, and the jobs from spool hold status, and the job had been active in main when it was put into spool hold status, the failure options are used to (JES3) cancel the job, place the job in operator hold, print the job and then place it into operator hold, or restart the job.

JESMSG=

Specifies whether JES3 suppresses WTOs and WTORs that are added to the JESMSGLG data set for TSO users, started tasks, or batch jobs. Suppressing the WTOs and WTORs added to the JESMSGLG data set significantly reduces the subsystem interface traffic and the number of spool I/O requests needed to support JESMSGLG logging.

NOTSO: Indicates that JES3 should not log WTOs and WTORs originating from TSO users in the JESMSGLG spool data set.
NOSTC: Indicates that JES3 should not log WTOs and WTORs originating from started tasks in the JESMSGLG spool data set.
NOBATCH: Indicates that JES3 should not log WTOs and WTORs originating from batch jobs in the JESMSGLG spool data set.
ALL: Indicates that JES3 should log all WTOs and WTORs in the JESMSGLG spool data set.
If you specify this parameter, you cannot specify any other parameter. If you do so, JES3 uses the default value of NOTSO.

If you specify an invalid sub-parameter, JES3 uses the parameter default of NOTSO.

Note: Using the JESMSG= keyword on the CLASS initialization statement overrides the JESMSG= specification on the STANDARDS initialization statement. The asynchronous nature of message processing results in the following situations:

JES3 is not able to guarantee the order of messages in the JESMSGLG.
It is possible that multi-line messages might have other messages interspersed within them.

LINES=

Defines the maximum number of lines to be printed for a single job and how to handle jobs exceeding this maximum.

nnn

Specifies the maximum number of lines, in thousands, from 1 to 999. The default is 1; that is, 1000 lines.

CANCEL or C

Specifies that a job be canceled if it exceeds nnn.

DUMP or D

Specifies that a job be canceled with a system abend dump is the job exceeds nnn.

WARNING or W

Specifies that JES3 issue a warning message and continue processing the job if it exceeds the line limit. JES3 reissues a warning message for every additional 500 (default) lines the job prints.

mmm or 50: Regulates the frequency that JES3 issues message IAT1600 after exceeding the maximum line limit (mmm is a percentage of the maximum line limit). The value you specify must be a multiple of 10 between 10 and 100 inclusive. Specifying too low a value can cause JES3 to flood the system with messages which in turn, can cause a shortage of staging areas and console buffers. To decrease the number of messages issued, use higher values for nnn and mmm. If you specify an invalid parameter, JES3 uses the parameter default.

If you specify an invalid subparameter, JES3 uses the parameter default.

MAXJOBST=

Specifies the maximum number of JCL statements that a batch job can include. JES3 control statements are not counted. This limit applies no matter where in the complex the job's C/I processing takes place. For a discussion about how to select the job JCL limit, see “Preventing a Job from Dominating the SWA” in z/OS JES3 Initialization and Tuning Guide.

nnn: Specifies the total number of JCL statements that a single job may contain and still be processed by a converter/interpreter (CI) DSP. nnn may be any decimal integer from 0 to 99999999, inclusive. Specifying 0 indicates that you do not want to limit the total number of JCL statements in a single job.

If you specify an invalid subparameter, JES3 uses the parameter default.

MAXASST=

Specifies the maximum number of JCL statements for batch jobs that may be processed concurrently by all CI DSPs in the JES3 global address space. The value must be an integer between 0 and 99999999, inclusive. A value of 0 means no JCL statement limit applies; JES3 does not check how many JCL statements are being processed. For guidelines on choosing a value for this parameter, see z/OS JES3 Initialization and Tuning Guide.

If you specify an invalid subparameter, JES3 uses the parameter default.

MAXINDD=

Specifies the maximum number of JCL SYSIN DD statements that a batch job can include. Only DD* and DD DATA DD statements are included in this count. Other types of DD statements are not counted. For a discussion about how to select the job SYSIN DD limit see "Preventing a Job from Dominating the JSAM Buffers" in z/OS JES3 Initialization and Tuning Guide.

nnn: Specifies the number of JCL SYSIN DD statements that a single job may contain and still be processed. nnn may be any decimal integer from 0 to 99999999, inclusive. Specifying 0 indicates that you do not want to limit the number of DD statements in a single job.
If you specify an invalid subparameter, JES3 uses the parameter default.

Note: The parameter default will be whatever value was specified for the MAXJOBST parameter, or the default value for MAXJOBST if MAXJOBST was not specified.

PRTY=

Specifies the default job priority (0 to 14) for a job whose priority is not specified in the JCL or on the CLASS statement.

If you specify an invalid subparameter, JES3 uses the parameter default.

SETUP=

Indicates the system standard for allocation of devices identified by the NAME parameter of SETNAME statement(s). The SETUP parameter specifies the type of setup processing, such as job setup, tape high watermark setup, or disk high watermark setup. This parameter also provides the default for the SETUP parameter on the //*MAIN JES3 statement and also, SETUP=NONE overrides the SETUP parameter on the //*MAIN statement.

NONE: Specifies that no preexecution setup is to occur. All devices are allocated, mounted, and deallocated by MVS; the SETPARAM statement is ignored. The SETUNITS and SETNAME tables are created even though MDS processing does not occur.
JOB: Specifies that preexecution setup is to occur by job for those devices (indicated in the UNIT parameter of DD statements for the job) which are identified in the SETNAME statement. All devices for the job are allocated to the job from first step to last. This type of setup improves job turnaround time at the expense of overall device usage efficiency.
DHWS: Specifies that high watermark setup is to occur for only MVS direct-access units identified in the SETNAME statement. The direct-access units must also be specified on the TYPE parameter of the HWSNAME statement. MDS will attempt to allocate the minimum number of direct-access devices for a job. Other devices are allocated based on the amount required for the entire job.
If you specify an invalid subparameter, JES3 uses the parameter default.
THWS: Specifies that high watermark setup is to occur for only tape units identified in the SETNAME statement. The tape units must also be specified on the TYPE parameter of the HWSNAME statement. MDS will attempt to allocate the minimum number of tape devices for a job. Direct-access devices are allocated based on the amount for the entire job.
HWS: Specifies that high watermark setup is to occur for all devices required for a job running on an MVS processor which are indicated in the SETNAME statement. The devices must also be specified on the TYPE parameter of the HWSNAME statement. MDS will attempt to allocate the minimum number of devices required for the job to run.

SYSLINES=

nnnn: Defines the maximum number of JESYSMSG message lines, in thousands, that are issued before the system issues message IAT1613. nnnn may be any decimal integer from 1 to 9999, inclusive. The default is 10 (10,000 messages). If you specify an incorrect value, JES3 uses the default.
mmm: The frequency at which JES3 issues message IAT1613 after exceeding the original SYSLINES limit. mmm is a percentage of the original SYSLINES limit. The value you specify must be a multiple of 10 between 10 and 100 inclusive. The default is 50 (50%). If you specify an incorrect value, JES3 uses the default.

Specifying values too low can cause JES3 to issue message IAT1613 prematurely or too frequently for normal conditions (for example, a long running started task). To decrease the number of IAT1613 messages issued, use higher nnnn and mmm values.

THWSSEP=

Specifies whether you want scratch and specific tape requests, or scratch tape requests of different media types separated during high watermark processing. This parameter is valid only when you specify the HWS or THWS parameter of the SETUP parameter.

You can use this parameter to direct specific and scratch tape requests to different types of tape drives. For example, you may want JES3 to allocate only scratch tape requests to an IBM® 3480 that is equipped with an automatic cartridge loader.

You can also use this parameter to direct scratch tape requests that have a preferred media type to different drives. JES3 attempts to allocate a device matching the media type whenever possible.

An end user can override this parameter using a //*MAIN JECL statement. The values also can be modified using the JES3 *MODIFY,S command. For information about using the JES3 *MODIFY,S command see z/OS JES3 Commands.

IGNORE: Specifies that JES3 not separate scratch and specific tape requests and not separate scratch tape requests of different media types during high watermark processing. Both scratch and specific tape requests and scratch requests of different media types can be allocated on the same tape drive.
PREFER: Specifies that JES3 attempt to allocate scratch and specific tape requests on separate tape drives and attempt to allocate scratch tape requests of different media types on separate tape drives without allocating additional devices. If JES3 cannot separate the requests, scratch and specific tape requests and scratch requests of different media types will be allocated on the same tape drive.
REQUIRE: Specifies that JES3 should not allocate scratch and specific tape requests on the same tape drive and not allocate scratch tape requests of different media types on the same tape drive, even if JES3 must allocate additional tape drives to satisfy the request.

INTPMID=

Specifies the 2-byte identifier (ID) of the converter/interpreter options list for jobs entered using the internal reader. The ID must match the ID specified by the PARMID parameter on a CIPARM initialization statement. If no CIPARM statements are included in the initialization stream, the default value is used.

If you specify an invalid subparameter, JES3 uses the parameter default.

STCPMID=

Specifies the 2-byte identifier of the parameter list to be used when interpreting started task jobs. The parameter list specified must be defined on a CIPARM statement.

TSOPMID=

Specifies the 2-byte identifier of the parameter list to be used when interpreting TSO LOGON jobs. The parameter list must be defined on a CIPARM statement.

For TSO-submitted jobs, the message class is determined as follows:

If the job has the MSGCLASS parameter coded on the job statement, the value specified on that parameter is used.
Otherwise, the message class is taken from the MSGCLASS or the HOLD (HOLDCLASS) parameters specified in the user's profile in either the TSO/E UADS or the TSO/E segment of the RACF® data base. The MSGCLASS parameter value is used as the message class if the job was submitted using the TSO/E SUBMIT jjj or SUBMIT jjj HOLD command. The HOLD (or HOLDCLASS) parameter value is used as the message class if the job was submitted using the TSO/E SUBMIT jjj HOLD command.
The specified or default message class from the CIPARM initialization statement associated with the INTPMID= parameter on the STANDARDS initialization statement.

For jobs submitted by another job through the internal reader (regardless of whether of not the submitting job is from TSO):

If the job has the MSGCLASS parameter coded on the JOB statement, the value specified on that parameter is used.
The SYSOUT class from the DD statement that specifies INTRDR.
The specified or default message class from the CIPARM initialization statement associated with the INTPMID= parameter on the STANDARDS initialization statement.

INTPROC=

Specifies the appropriate IATPLBxx procedure library to be searched by the MVS converter when resolving procedure references for jobs submitted using the internal reader. This procedure library must be defined by an IATPLBxx DD statement in the JES3 start procedure or by a DYNALLOC initialization statement. An individual job can override this value using the PROC parameter on the //*MAIN JES3 control statement.

Note: Jobs entering from a disk reader or NJERDR use the standard procedure library as defined on the IATPLBST DD statement in the JES3 procedure or from the DYNALLOC initialization statement.

If you specify an invalid subparameter, JES3 uses the parameter default.

STCPROC=

Specifies the appropriate IATPLBxx procedure library used for started task jobs. This procedure library must be defined by a IATPLBxx DD statement in the JES3 procedure or a DYNALLOC initialization statement. The default is IATPLBST.

TSOPROC=

Specifies the appropriate IATPLBxx procedure library to be used for TSO LOGON jobs. This procedure library must be defined on a IATPLBxx DD statement or a DYNALLOC statement. The default procedure library is IATPLBST.

BYTES=

Specifies the maximum number of bytes of data that can be written to a spool data set for a job and the action to be taken for any job that exceeds the maximum.

nnnnnn

Specifies the maximum number of bytes of data that can be written to a spool data set for a job. The value specified must be between 1 and 999999, inclusive, and represents thousands of bytes (that is, 1000 times nnnnnn) of spool data. This value may be overridden by the BYTES parameter on the //*MAIN JES3 job control statement.

C or CANCEL

Specifies that a job whose output exceeds the byte limit is to be canceled without a dump.

D or DUMP

Specifies that a job whose output exceeds the byte limit is to be canceled with a system abend dump.

W or WARNING

Specifies that JES3 issue a warning message and continue processing the job if it exceeds the byte limit. JES3 reissues a warning message for every additional 750,000 (default) bytes the job writes to spool.

mmm or 50: Regulates the frequency that JES3 issues message IAT1600 after exceeding the maximum number bytes (mmm is a percentage of the maximum byte limit). The value you specify must be a multiple of 10 between 10 and 100 inclusive. Specifying too low a value can cause JES3 to flood the system with messages which in turn, can cause a shortage of staging areas and console buffers. To decrease the number of messages issued, use higher values for nnnnnn and mmm.

If you specify an invalid subparameter, JES3 uses the parameter default.

PAGES=

Specifies the maximum number of pages for a single job, and the action to be taken for any job whose output exceeds the maximum.

nnnnnnnn

Specifies the maximum number of pages for a single job. This value may be overridden by the PAGES parameter on the //*MAIN JES3 job control statement. The specified number must be between 1 and 16777215, inclusive.

C or CANCEL

Specifies that a job whose output exceeds the page limit is to be canceled without a dump.

D or DUMP

Specifies that a job whose output exceeds the page limit is to be canceled with a system abend dump.

W or WARNING

Specifies that JES3 issue a warning message and continue processing the job if it exceeds the page limit. JES3 reissues a warning message for every additional 250 (default) pages that the output exceeds the limit.

mmm or 50: Regulates the frequency that JES3 issues message IAT1600 after exceeding the maximum page limit (mmm is a percentage of the maximum page limit). The value you specify must be a multiple of 10 between 10 and 100 inclusive. Specifying too low a value can cause JES3 to flood the system with messages which in turn, can cause a shortage of staging areas and console buffers. To decrease the number of messages issued, use higher values for nnnnnnnn and mmm.

If you specify an invalid subparameter, JES3 uses the parameter default.