Parameter definition

ACMAIN=processor-id

Identifies the job with the specified processor, even though the job was not submitted from or run on that processor. ACMAIN allows:

Sysout data sets to be sent to a userid attached to the specified processor. The userid must be named in the USER parameter. The ACMAIN parameter applies to all sysout data sets for the job.
Receipt of notification that a job you submitted through batch processing has completed by coding the ACMAIN parameter on a JES3 //*MAIN statement in addition to the JOB statement NOTIFY parameter. The ACMAIN parameter names the processor that you, the TSO/E user, are logged onto.

processor-id: Requests a processor in the complex.

BYTES=([nnnnnn][,WARNING][,mmm])

BYTES=([nnnnnn][,W][,mmm])

BYTES=([nnnnnn][,CANCEL])

BYTES=([nnnnnn][,C])

BYTES=([nnnnnn][.DUMP])

BYTES=([nnnnnn][,D])

Specifies the maximum number of bytes of data to be spooled from this job’s sysout data sets and the action to be taken if the maximum is exceeded.

If BYTES is not specified, the installation default for this job class applies.

nnnnnn

Specifies the number of bytes in thousands. nnnnnn is 1 through 6 decimal numbers from 1 through 999999.

WARNING or W

If the maximum is exceeded, requests that JES3 issue an operator warning message and continue processing.

Any messages about this parameter following the warning message will reflect the number specified on the STANDARD initialization statement or the system default, not the specified maximum.

mmm: Specifies the frequency that an operator warning message is to be issued after the maximum specified by nnnnnn is exceeded. mmm is a multiple of 10 in the range 10 to 100. mmm is a percentage of nnnnnn that is used to calculate the number of additional bytes between warning messages. For example, if BYTES=(100,W,20) is specified, the first warning message is sent to the operator when 100,000 bytes of sysout data is reached. Subsequent warning messages are sent when each additional 20 percent of 100,000 is reached (at 120,000 bytes, 140,000 bytes, and so on). Messages are sent until the job ends or the operator cancels the job.

CANCEL or C

If the maximum is exceeded, requests that JES3 cancel the job.

DUMP or D

If the maximum is exceeded, requests that JES3 cancel the job and ask for a storage dump.

CARDS=([nnnn][,WARNING][,mmm])

CARDS=([nnnn][,W][,mmm])

CARDS=([nnnn][,CANCEL])

CARDS=([nnnn][,C])

CARDS=([nnnn][,DUMP])

CARDS=([nnnn][,D])

Specifies the maximum number of cards to be punched from this job’s sysout data sets and the action to be taken if the maximum is exceeded.

If you specify CARDS=0 the zero applies only to the quantity of punched output; it does not cancel the action to be taken if the maximum is exceeded. If a record is then sent to a punch, JES3 will warn, cancel, or dump, depending on the second parameter.

Note: When punching dump output, JES3 ignores CARDS=0.

If CARDS is not specified, the installation default for this job class is used.

nnnn

Specifies the number of cards in hundreds. nnnn is 1 through 4 decimal numbers from 1 through 9999.

WARNING or W

If the maximum is exceeded, requests that JES3 issue an operator warning message and continue processing.

Any subsequent messages about this parameter will reflect the number specified on the STANDARD initialization statement or the system default, not the maximum specified in the CARDS parameter.

mmm: Specifies the frequency that an operator warning message is to be issued after the maximum specified by nnnn is exceeded. mmm is a multiple of 10 in the range 10 to 100. mmm is a percentage of nnnn that is used to calculate the number of additional cards between warning messages. For example, if CARDS=(100,W,20) is specified, the first warning message is sent to the operator when 10,000 cards of sysout data is reached. Subsequent warning messages are sent when each additional 20 percent of 10,000 is reached (at 12,000 cards, 14,000 cards, and so on). Messages are sent until the job ends or the operator cancels the job.

CANCEL or C

If the maximum is exceeded, requests that JES3 cancel the job.

DUMP or D

If the maximum is exceeded, requests that JES3 cancel the job and ask for a storage dump.

CLASS=class-name

Specifies the job class for this job. class-name is 1 through 8 characters.

If the desired class-name is a single-character, you can specify it on the //*MAIN statement or the JOB statement.

JES3 uses the following, in override order, to assign the job to a class:

//*MAIN statement CLASS parameter
JOB statement CLASS parameter
The default class, which is defined during JES3 initialization.

If neither CLASS nor LREGION is specified, JES3 determines the logical region size based on initialization parameters.

DEADLINE=(time,type[,date])

DEADLINE=(time,type[,rel,cycle])

Specifies when the job is required.

When you specify the current date but submit the job after the specified time, JES3 changes the priorities to make the job the same priority level it would have if it had been submitted before the deadline but not completed.

Attention: Deadline scheduling can interfere with dumping a portion of the job queue. For example, if JOB A is waiting to be scheduled, has a priority of 7, and, in one minute, is due to have its priority increased to 9, JOB A could be missed by dump job processing, if the dump job facility is dumping the entire job queue and currently dumping priority 8 jobs. The dump job facility processes the jobs with the highest priority first. If the dump job facility does not finish processing priority 8 jobs before JOB A becomes priority 9, JOB A will not be dumped.

Deadline scheduling information is not sent with a job when the job is transferred via NJE to another node; the destination node may use different deadline scheduling algorithms, if any.

time

Specifies the deadline time, expressed as one of the following:

nM: The job is to be scheduled within n minutes. n is 1 through 4 numbers from 0 through 1440.
nH: The job is to be scheduled within n hours. n is 1 or 2 numbers from 0 through 24.
hhhh: The job is to be scheduled by the time of day, hhhh, in 24-hour clock time (0800 is 8:00 a.m.). hhhh is from 0000 (start of the day) through 2400 (end of the day).

type

Identifies the deadline algorithm. The deadline algorithm is defined by the installation, controls how the job’s priority is increased, and is one character: A through Z or 0 through 9. If the specified algorithm is not defined, JES3 abnormally terminates the job.

date

Specifies the date, in one of the following formats, when the time parameter takes effect.

mmddyy: where mm is the month (01-12), dd the day (01-31), and yy the 2-digit year (01-99).
mm/dd/yyyy: where mm is the month (01-12), dd the day (01-31), and yyyy the 4-digit year (for example, 1999). Leading zeroes are required in the day and month fields.

Note:

For dates in the format of mmddyy, a century of ‘19’ is assumed.
For dates in the format of mmddyy, a date of ‘00’ is not allowed.
For dates of January 1, 2000 and later, you must use the form mm/dd/yyyy.
If both date and rel,cycle are omitted, JES3 assumes (1) the current date, if the deadline time is later in the day, or (2) the next day’s date, if the deadline time has already past today.

rel

Specifies on which day within a cycle the deadline falls. rel is 1 through 3 numbers from 1 through 366. The value of rel depends on the specified cycle, as follows:

WEEKLY: Sunday is day 1; Saturday is day 7. If rel is greater than 7, it defaults to 7.
MONTHLY: Day 1 is the first day of the month. Days 29, 30, and 31 are treated as the last day of the month. If rel is greater than 31, it defaults to 31.
YEARLY: Day 1 is January 1; day 365 is December 31, for non-leap years, and day 366 is December 31, for leap years. If rel is greater than 365, it defaults to 365 for non-leap years or 366 for leap years.

cycle

Specifies the length of a cycle. cycle is coded as WEEKLY, MONTHLY, or YEARLY.

For example, DEADLINE=(1200,B,1,WEEKLY) indicates that the job reaches its deadline at 12 noon on Sunday. This job would be submitted once a week for it to be processed every Sunday.

EXPDTCHK=YES

EXPDTCHK=NO

Indicates whether or not JES3 is to perform expiration date checking for scratch output tape volumes with IBM® standard labels (SL).

YES: Requests expiration date checking. Tape volumes premounted for SL scratch requests must have expired dates.
NO: Requests that expiration dates not be checked.

FAILURE=RESTART

FAILURE=CANCEL

FAILURE=HOLD

FAILURE=PRINT

Indicates the job recovery option to be used if the system fails. If you do not code a FAILURE parameter on the //*MAIN statement, JES3 assigns the job the default failure option, which is defined during JES3 initialization for each job class. (See also the RD parameter on the JOB statement.)

Note: If a job is registered with the automatic restart manager (ARM) at the time of a system failure, ARM determines whether to restart the job, regardless of the value specified on the FAILURE keyword.

If the ARM restarts the job, JES discards all non-spin sysout data sets created during the previous execution. (You can avoid losing that output by adding SPIN=UNALLOC to the DD statement for the SYSOUT data set.)

RESTART: Requests that JES3 restart the job when the failing processor is restarted. Do not specify RESTART for jobs that use the DEQ at DEMOUNT facility for tape volumes.
CANCEL: Requests that JES3 print the job and then cancel the job.
HOLD: Requests that JES3 hold the job for restart.
PRINT: Requests that JES3 print the job and then hold the job for restart.

FETCH=ALL

FETCH=NONE

FETCH=SETUP

FETCH=(ddname[,ddname]...)

FETCH=/(ddname[,ddname]...)

Determines the fetch messages that will be issued to the operator for disk and tape volumes for this job.

If FETCH is not specified, the installation default for this job class applies.

ALL: Requests that JES3 issue fetch messages to the operator for all removable volumes specified in DD statements that request JES3-setup devices. This subparameter does not apply to permanently resident volumes.
NONE: Requests that JES3 not issue fetch messages.
SETUP: Requests that JES3 issue fetch messages to the operator for the volumes specified in all DD statements identified in the //*MAIN SETUP parameter. If you code FETCH=SETUP without also coding the //*MAIN SETUP parameter, JES3 will issue fetch message as though you had specified FETCH=ALL.
ddname: Requests that JES3 issue fetch messages for only the volumes specified in DD statement ddname.
If you code a list of ddnames and the list cannot be contained on a single statement, FETCH= must be repeated on the continuation statement.
/ddname: Requests that JES3 not issue fetch messages for any volumes specified in DD statement ddname.

HOLD=YES

HOLD=NO

YES: Indicates that the job is to enter the system in operator-hold status and be withheld from processing until the operator requests its release. However, if an error occurs during input service processing, the job is not held for operator intervention.
This parameter has the same function as TYPRUN=HOLD on the JOB statement.
NO: Indicates that the job is to enter the system normally. Processing does not require operator intervention. If the HOLD parameter is omitted, NO is the default.

IORATE=MED

IORATE=HIGH

IORATE=LOW

Indicates the I/O-to-processor ratio for a job. Use this parameter to balance the mixture of jobs selected for execution on the processor.

If you do not code an IORATE parameter on the //*MAIN statement, JES3 assigns the job the default I/O-to-processor ratio, which is defined during JES3 initialization for each job class.

JOURNAL=YES

JOURNAL=NO

Indicates whether or not JES3 is to create a job journal for the job.

If JOURNAL is omitted, JES3 uses an installation default specified at initialization. If you use the automatic restart manager (ARM) to restart a job, you do not need to save the journal because ARM does not use the job journal when restarting jobs.

YES: Indicates that the job is to have a job journal.
NO: Indicates that the job is not to have a job journal.

LINES=([nnnn][,WARNING][,mmm])

LINES=([nnnn][,W][,mmm])

LINES=([nnnn][,CANCEL)

LINES=([nnnn][,C])

LINES=([nnnn][,DUMP])

LINES=([nnnn][,D])

Indicates the maximum number of lines of data to be printed from this job’s sysout data sets and the action to be taken if the maximum is exceeded.

If you specify LINES=0 the zero applies only to the number of lines; it does not cancel the action to be taken if the maximum is exceeded. If a record is sent to be printed, JES3 will warn, cancel, or dump, depending on the second parameter.

Note: JES3 ignores any line count specification when printing the output for a SYSABEND or SYSUDUMP sysout data set.

If LINES is not specified, the installation default for this job class applies. The installation default is specified on the OUTLIM parameter of the OUTSERV JES3 initialization statement.

nnnn

Specifies the number of lines, in thousands. nnnn is 1 through 4 decimal numbers from 1 through 9999.

WARNING or W

If the maximum is exceeded, requests that JES3 issue an operator warning and continue processing.

Any messages about this parameter following the warning message will reflect the number specified on the STANDARD initialization statement or the system default, not the maximum specified in the LINES parameter.

mmm: Specifies the frequency that an operator warning message is to be issued after the maximum specified by nnnn is exceeded. mmm is a multiple of 10 in the range 10 to 100. mmm is a percentage of nnnn that is used to calculate the number of additional lines between warning messages. For example, if LINES=(100,W,20) is specified, the first warning message is sent to the operator when 100,000 lines of sysout data is reached. Subsequent warning messages are sent when each additional 20 percent of 100,000 is reached (at 120,000 lines, 140,000 lines, and so on). Messages are sent until the job ends or the operator cancels the job.

CANCEL or C

If the maximum is exceeded, requests that JES3 cancel the job.

DUMP or D

If the maximum is exceeded, requests that JES3 cancel the job and ask for a storage dump.

LREGION=nnnnK

Specifies the approximate size of the largest step’s working set in real storage during execution. LREGION (logical region) is used by JES3 to improve scheduling on the processor. The nnnn is 1 through 4 decimal numbers that indicate the size in kilobytes (1 kilobyte = 1024 bytes).

If neither CLASS nor LREGION is coded, JES3 determines the logical region size based on initialization parameters.

Use the LREGION parameter carefully. If the values selected for LREGION are too small, the job may take longer to run.

ORG=group-name

ORG=nodename[.remote]

Indicates that the job’s sysout data sets are to be directed to the named group or network node. Otherwise, the job’s sysout data sets are directed to the group of devices or node from which the job originated.

group-name: Specifies an origin group.
nodename: Specifies a network node. nodename is 1 through 8 characters.
remote: Specifies a remote work station or VM userid. remote is 1 through 8 characters and must be separated from the nodename by a period.

Overriding an ORG Parameter: If you do not want a particular data set in the job to go to the destination on the ORG parameter, change its destination in one of the following ways:

If the sysout data set is not scheduled to a held class, you can override the ORG parameter destination with the DEST parameter on a //*FORMAT, OUTPUT JCL, or DD statement.
If the sysout data set is scheduled to a held class, you can override the ORG parameter destination with the DEST parameter on an OUTPUT JCL, or DD statement.

JES3 ignores the ORG parameter for a dynamically-allocated SYSOUT data set.

PAGES=([nnnnnnnn][,WARNING][,mmm])

PAGES=([nnnnnnnn][,W][,mmm])

PAGES=([nnnnnnnn][,CANCEL])

PAGES=([nnnnnnnn][,C])

PAGES=([nnnnnnnn][,DUMP])

PAGES=([nnnnnnnn][,D])

Indicates the maximum number of pages to be printed for this job’s sysout data sets and the action to be taken if the maximum is exceeded.

If PAGES is not specified, the installation default for this job class applies.

nnnnnnnn

Specifies the number of pages. nnnnnnnn is 1 through 8 decimal numbers from 1 through 16777215.

WARNING or W

If the maximum is exceeded, requests that JES3 issue an operator warning message and continue processing.

Any messages about this parameter following the warning message will reflect the number specified on the STANDARD initialization statement or the system default value, not the maximum specified in the PAGES parameter.

mmm: Specifies the frequency that an operator warning message is to be issued after the maximum specified by nnnnnnnn is exceeded. mmm is a multiple of 10 in the range 10 to 100. mmm is a percentage of nnnnnnnn that is used to calculate the number of additional pages between warning messages. For example, if PAGES=(1000,W,20) is specified, the first warning message is sent to the operator when 1,000 pages of sysout data is reached. Subsequent warning messages are sent when each additional 20 percent of 1,000 is reached (at 1,200 pages, 1,400 pages, and so on). Messages are sent until the job ends or the operator cancels the job.

CANCEL or C

If the maximum is exceeded, requests that JES3 cancel the job.

DUMP or D

If the maximum is exceeded, requests that JES3 cancel the job and ask for a storage dump.

PROC=ST

PROC=xx

Names the procedure library that the system is to search for cataloged procedures called by EXEC statements in the job. If a procedure cannot be found in the named library, JES3 abnormally terminates the job.

If this parameter is omitted, the default depends on the source of the job. If the job is submitted as a batch job, the default is ST. If the job is submitted from an internal reader, the default can be another procedure library, as specified by the installation on the STANDARDS initialization statement (the INTPROC, STCPROC, or TSOPROC parameters).

ST: Indicates the standard procedure library: SYS1.PROCLIB.
xx: Identifies the last 2 characters of the ddname of a procedure library. xx is defined by the installation (IATPLBxx) in the procedure used to start JES3. If this parameter is coded, only the specified library is searched; SYS1.PROCLIB is not searched.

RINGCHK=YES

RINGCHK=NO

Indicates whether or not JES3 is to check the status of the tape reel ring for tape devices set up by JES3.

YES: Indicates that a validation check is to be made. If the RINGCHK parameter is omitted, YES is the default.
NO: Indicates that ring checking is to be by-passed for this job.

SETUP=JOB

SETUP=HWS

SETUP=THWS

SETUP=DHWS

SETUP=(stepname.ddname[,stepname.ddname]...)

SETUP=

(stepname.procstepname.ddname[,stepname.procstepname.ddname]...)

SETUP=/(stepname.ddname[,stepname.ddname]...)

SETUP=

/(stepname.procstepname.ddname[,stepname.procstepname.ddname]...)

Modifies the standard setup algorithm used in assigning devices to a job before its execution.

If SETUP is omitted, JES3 assigns mountable tape and disk volumes based on an installation default defined at initialization.

JOB

Requests job setup, which is allocation of all JES3-managed devices required in the job before the job executes. JES3 mounts the initial volumes necessary to run all steps before the job executes. JOB overrides the SETUP parameter on the JES3 STANDARDS initialization statement.

HWS

Requests high watermark setup, which is allocation of the minimum number of devices required to run the job. The minimum number is equal to the greatest number of devices of each type needed for any one job step. High watermark setup does not cause premounting of all mountable volumes.

THWS

Requests high watermark setup for tapes but job setup for disks.

DHWS

Requests high watermark setup for disks but job setup for tapes.

stepname.ddname

stepname.procstepname.ddname

Specifies explicit setup, which is allocation of the volumes needed for a DD statement before the job executes. JES3 premounts the indicated volumes. When requesting explicit setup, specify enough devices so that JES3 can allocate all the required devices at any one time. If too few devices are specified, JES3 cancels the job.

Use form stepname.ddname to indicate DD statement, ddname, in step, stepname, in this job. Use form stepname.procstepname.ddname to indicate DD statement, ddname, in procedure step, procstepname, of a procedure that is called by a step, stepname, in this job. The ddname must match exactly the ddname on the DD statement. (See the example for the //*DATASET statement.)

If you code a list of ddnames and the list cannot be contained on a single statement, SETUP= must be repeated on the continuation statement.

/stepname.ddname

/stepname.procstepname.ddname

Requests that JES3 not explicitly set up any volumes specified in DD statement ddname.

SPART=partition-name

Indicates the spool partition in which JES3 is to allocate spool space to this job.

partition-name: Specifies the name of the spool partition. partition-name is 1 through 8 characters and must match a partition name specified during JES3 initialization. If the name does not match, JES3 ignores the SPART parameter and uses the installation default.

The SPART parameter does not affect allocation for the sysout data sets for the job; these data sets always go to the spool partitions specified during JES3 initialization for the output classes.

If SPART is not specified, JES3 allocates spool data sets to a partition, as follows, in override order:

The spool partition for the job’s class.
The spool partition for the processor executing the job.
The default spool partition.

SYSTEM=ANY

SYSTEM=JGLOBAL

SYSTEM=JLOCAL

SYSTEM=(main-name[,main-name]...)

SYSTEM=/(main-name[,main-name]...)

Indicates the processor that is to execute this job. If a specific processor is named, the processor name must also be specified on the CLASS initialization statement for the job class.

ANY: Indicates any global or local system that satisfies the job’s requirements.
JGLOBAL: Indicates that the job is to run on the global processor only.
JLOCAL: Indicates that the job is to run on a local processor only.
main-name: Indicates that the job is to run on the named processor or processors.
/main-name: Indicates that the job is not to run on the named processor or processors.

Need for SYSTEM Parameter: If you omit a SYSTEM parameter, the job runs on the processor used for the job’s class. Usually a SYSTEM parameter is not needed. However, if any DD statement UNIT parameter in the job specifies a device-number, a SYSTEM parameter must be coded. JES3 ignores the SYSTEM parameter if either the SYSTEM or SYSAFF parameter is specified on the JOB statement.

Parameter Agreements: The following parameters must be consistent with the SYSTEM parameter or JES3 will terminate the job:

CLASS parameter on the JOB or //*MAIN statement. The requested processor must be assigned to execute jobs in the specified class.
All devices specified on DD statement UNIT parameters must be available to the requested processor.
TYPE parameter on the //*MAIN statement must specify the system running on the requested processor.
Dynamic support programs requested on //*PROCESS statements must be able to be executed on the requested processor.

THWSSEP=IGNORE

THWSSEP=PREFER

THWSSEP=REQUIRE

Indicates whether or not you want scratch tape requests and specific tape requests separated and whether you want scratch tapes of different media types separated during high watermark processing. This parameter is valid only if high watermark setup (HWS or THWS) is specified on the SETUP parameter or defined at JES3 initialization.

Use this parameter to direct scratch and specific tape requests to different 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).

If you omit THWSSEP, JES3 uses an installation default defined at initialization.

IGNORE: Specifies that JES3 is not to 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 tape requests of different media types are 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.

TRKGRPS=(primary-qty,second-qty)

Specifies the number of track groups to be assigned to the job. A track group is a number of spool space allocation units. The size of the track group is defined in the GRPSZ parameter on the JES3 BUFFER or SPART initialization statement.

primary-qty: Specifies the number of track groups to be initially allocated. This quantity is one decimal number from 1 through 9.
second-qty: Specifies the number of track groups to be allocated when the currently allocated groups are filled and more space is needed. This quantity is one decimal number from 1 through 9.

The //*MAIN TRKGRPS parameter overrides a TRKGRPS parameter on the CLASS or MAINPROC initialization statement. However, when a sysout DD statement specifies an output class, the TRKGRPS parameter for that output class overrides the //*MAIN TRKGRPS parameter.

TYPE=ANY

TYPE=VS2

Indicates the control program that is to execute this job. If you omit a TYPE parameter, the job runs under the control program used for the job’s class.

ANY: Indicates that JES3 is to use any control program that satisfies the job’s requirements. In present systems, JES3 schedules the job on MVS™.
VS2: Indicates that JES3 is to schedule the job on MVS.

UPDATE=(dsname[,dsname]...)

Identifies the procedure library data set(s) that this job is to update. This parameter causes all jobs using the identified data set and any concatenated data sets to be held until the update is complete. See z/OS JES3 Initialization and Tuning Guide for information about updating procedure libraries.

dsname: Specifies the data set name. The identified data set cannot be concatenated to another data set.

Note: If a data set is dynamically allocated as both a JES3 DISKRDR data set and a JES3 PROCLIB data set, the UPDATE = parameter (JES3 procedure library update facility) cannot be used to move the data set.

USER=userid

Identifies the job with the specified TSO/E user, even though the job was not submitted via TSO/E by that user. USER allows:

The TSO/E userid, interacting with a global or local processor, to issue the TSO/E OUTPUT command to access sysout data sets from the job. If the job executes on one processor and the TSO/E userid is attached to another processor, the ACMAIN parameter must identify the processor for the TSO/E userid.
The TSO/E userid, interacting with any processor, to inquire about the status of the job or to cancel the job.

userid: Identifies a TSO/E user. userid is 1 through 7 alphanumeric or national ($, #, @) characters.