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


Parameters

z/OS JES3 Initialization and Tuning Reference
SA32-1005-00

ADDRSORT=
Specifies the order in which JES3 MDS allocates devices.
NO
Indicates that devices within a device type are to be allocated in the same order as the DEVICE statements are placed in the initialization stream.
YES
Indicates that devices within a device type are to be allocated by the order of their device numbers, that is, 188, 189, 18A.

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

ALLOCATE=
Specifies whether automatic allocation of a job is to immediately follow MDS volume fetch. This parameter is ignored for jobs that reference only premounted volumes. The FETCH parameter specified may override the ALLOCATE parameter.
MANUAL
Indicates that all jobs are to be suspended following volume fetch until the operator causes them to continue. Note that ALLOCATE=MANUAL is ignored if FETCH=NO is indicated; ALLOCATE=AUTO is assumed instead.
AUTO
Specifies that MDS will automatically attempt allocation of resources for all eligible jobs. If a job requires SMS-managed resources and you specify ALLOCATE=AUTO, MDS sends the job through the system select phase before allocation to determine which mains have access to the required SMS-managed resources. Note that ALLOCATE=AUTO is assumed (ALLOCATE=MANUAL is ignored) if FETCH=NO is specified.

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

DAFETCH=
Specifies the routing information for direct-access volume fetch messages.
msgdest
Specifies a SETUP-related console destination class. Direct-access volume fetch messages are issued with the routing code equivalent of this destination class.
NONE
indicates that volume fetch messages are not to be issued.
97
Indicates that volume fetch messages are to be issued with routing code 97; messages also are recorded on the hard-copy log. Note that this parameter is ignored if FETCH=NO is also specified.

97 is the routing code equivalent of JES3 Dest Class S1.

nnn
Specifies an MVS™ routing code from 1 to 28, or 41 to 128. Routing codes 29 through 40 are reserved for IBM's use and will be ignored if specified.
DEFERCT=
Specifies whether jobs requiring deferred mounts (whether explicitly requested through JCL, or implicitly requested because of using tape library devices) should be included in the CLASS/SELECT SDEPTH counts. The default is DEFERCT=NO.
DSN=
Specifies the number of characters (0 to 44) of the data set name that is to be included in MDS volume fetch, mount, and breakdown messages. This parameter is used for message formatting. If DSN=0 is specified, or assumed by default, then the data set name is omitted from these MDS messages.

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

FETCH=
Indicates whether MDS is to issue volume fetch messages. Note that the FETCH parameter can override the ALLOCATE parameter.
NO
Specifies that MDS is not to issue volume fetch messages. If FETCH=NO is specified, ALLOCATE=MANUAL will be overridden (and ALLOCATE=AUTO assumed); MDS will automatically attempt to set up jobs.
YES
Indicates that MDS is to issue volume fetch messages

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

MDSLOG=
Specifies the routing information for all non-action messages (that is, job LOGON and error messages).
msgdest
Specifies a SETUP-related console destination class. Non-action messages are issued with the routing code equivalent of this destination class.
97
Indicates that non-action messages are to be issued with routing code 97.

97 is the routing code equivalent of JES3 Dest Class S1.

nnn
Specifies an MVS routing code from 1 to 28, or 41 to 128. Routing codes 29 through 40 are reserved for IBM's use and will be ignored if specified.
MTJESMSG=
Specifies whether you want FETCH, ALLOCATION, and BREAKDOWN messages for mountable devices to appear in the JESMSGLG data set.
FETCH
Specifies that you want fetch messages for mountable devices written into the JESMSGLG data set.
ALLOC
Specifies that you want allocation messages for mountable devices written into the JESMSGLG data set.
BREAKDWN
Specifies that you want breakdown messages for mountable devices written into the JESMSGLG data set.
ALL
Specifies that you want fetch, allocation, and breakdown messages for mountable devices written into the JESMSGLG data set.
NONE
Specifies that you do not want fetch, allocation, or breakdown messages for mountable devices written into the JESMSGLG data set.

When you use the default (ALLOC and BREAKDWN), allocation and breakdown messages for mountable devices are written into the JESMSGLG data set.

PRJESMSG=
Specifies whether you want FETCH and ALLOCATION messages for permanently resident or reserved DASD to appear in the JESMSGLG data set.
FETCH
Specifies that you want fetch messages for permanently resident or reserved DASD written into the JESMSGLG data set.
ALLOC
Specifies that you want allocation messages for permanently resident or reserved DASD written into the JESMSGLG data set.

If this value is specified, an allocation message will be written for all non-mountable requests in addition to permanently resident DASD.

ALL
Specifies that you want both fetch and allocation messages for permanently resident or reserved DASD and allocation messages for all other devices written into the JESMSGLG data set .
NONE
Specifies that you do not want fetch or allocation messages for permanently resident or reserved DASD written into the JESMSGLG data set.

If this value is specified, an allocation message will not be written for all non-mountable requests in addition to permanently resident DASD.

REMOUNT=
Specifies the number of times that an operator can retry to correct volume mount errors for a job before the devices for the job are released and allocation is restarted. The value of nnn specifies the number of retries allowed, from 0 to 255. For example, if REMOUNT=1 is specified, the operator can make two attempts to mount the volume—the original mount request and one retry request.

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

SDEPZERO=
Indicates whether jobs that require a tape mount, but are in a CLASS, are defined as SDEPTH=0, should wait on the MDS allocate queue, the default, or be sent to the MDS error queue.
SMSSETUP=
Specifies whether JES3 manages system managed storage (SMS) data sets.
NO
Indicates that SMS data sets are not to be managed by JES3.
YES
Indicates that SMS data sets are to be managed by JES3.

If you specify an incorrect subparameter or do not specify the SMSSETUP= parameter, MVS determines whether JES3 manages SMS data sets or not.

TAFETCH=
Specifies the routing information for tape volume fetch messages. The first operand specifies the routing information for specific (nonscratch) volume requests. The second operand specifies the routing information for scratch volume requests.
msgdest
Specifies a SETUP-related console destination class. Tape volume (scratch or nonscratch) fetch messages are issued with the routing code equivalent of this destination class.
NONE
indicates that volume fetch messages are not to be issued.
97
Indicates that volume fetch messages are to be issued with routing code 97; messages also are recorded on the hard-copy log. Note that this parameter is ignored if FETCH=NO is also specified.

97 is the routing code equivalent of JES3 Dest Class S1.

nnn
Specifies an MVS routing code from 1 to 28, or 41 to 128. Routing codes 29 through 40 are reserved for IBM's use and will be ignored if specified.
ALWIO=
The ALWIO parameter specifies the current number of asynchronous I/O requests which can be processed concurrently. This value must be a number from 1 to the value specified in the MAXIO parameter. The value specified in the ALWIO parameter must be less than or equal to the value specified in the MAXIO parameter.

This parameter can be displayed through the *INQUIRY,S,ALWIO=nn command, and modified through the *MODIFY,S,ALWIO=nn operator command.

MAXIO=
The MAXIO parameter specifies the maximum number of asynchronous I/O requests that can be processed concurrently. Storage is obtained for the number of requests specified here. Note that an increase of one in this parameter results in a 76-byte increase in storage used. This parameter can only be changed when performing a warm start or cold start. The value specified in the MAXIO parameter may be a number from 1 to 99. The default value is 25.

The value specified in the MAXIO parameter must be greater than or equal to the value specified in the ALWIO parameter.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014