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

DUMP=
Indicates the type of MVS™ system dump to be taken in the event of an abnormal termination of JES3 or program check. The JES3 control blocks, if written, are formatted and always written to the JESABEND data set.
PRDMP
Specifies that a dump of main storage is to be written to the MVS SYS1.DUMPxx data set. To print this dump, use the MVS interactive problem control system (IPCS).

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

DUPJOBNM=
Indicates whether multiple batch jobs with the same name can be active in the MAIN SE.
YES
Specifies that multiple batch jobs with the same name are allowed to be scheduled for MAIN.

Use the Modify command, *MODIFY,Q,DUPJOBNM= , to change the value. The result of the command is checkpointed which effectively overrides the parameter until the next warmstart, coldstart or hotstart with refresh. See z/OS JES3 Commands for a detailed description of the command.

NO
Specifies that only one batch job of a certain name may be active in MAIN. DUPJOBNM=NO is the default keyword value.

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

DUPLOGON=
Indicates whether duplicate TSO/E logons across multiple systems in the JES3 complex are allowed.
YES
Specifies that a TSO/E logon for a specific user ID can be active on each system in the JES3 complex.
NO
Specifies that only one instance of a TSO/E logon for a specific user ID can be active in the JES3 complex. NO is the default.
If you specify an invalid subparameter, JES3 uses the parameter default.
DUMPLINS=
Specifies the maximum number of lines to be printed in a formatted dump. The maximum value allowed is 999999.
WANTDUMP=
Indicates the action taken when a JES3 failure condition occurs.
YES
Specifies that a dump should be taken when a failure occurs.
LIMIT
The maximum number of failures within the interval before JES3 temporarily changes to WANTDUMP=ASK. The acceptable value is a number between 2 and 10 or a zero. The default value is 3. Zero (0) indicates no limit will be used.
INTERVAL
A time period, in minutes, that will be used as the basis for the limit. The interval is a sliding window that ends at the time of the latest JES3 failure. The acceptable value is a number between 2 and 60 or a zero. The default value is 10. Zero (0) indicates no limit will be used.

If you run with WANTDUMP=YES, JES3 will override it by temporarily changing to WANTDUMP=ASK if more than LIMIT failures occur within the previous INTERVAL minutes.

NO
Specifies that no dump should be taken when a failure occurs.
ASK
Specifies that, when a failure occurs, the operator is to be given the choice of specifying whether a dump is to be taken.

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

INTRDR=
Specifies the maximum number of internal readers that can be active concurrently. Specifying too high a value can cause a shortage of JSAM buffers. You can specify any value between 1 and 999 inclusive for the variable nnn.

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

JOBNO=
Indicates a specific range of numbers for JES3 to assign to jobs that enter the JES3 complex. There must be at least five job numbers in this range. When the end of the range is reached, numbering resumes at the beginning of the range, skipping those numbers that are assigned to jobs still in the system. If all job numbers are assigned, JES3 suspends processing and issues a message that informs the operator that no job numbers are available. Note that JES3 can assign incoming jobs with job numbers higher than the number of jobs that input service can actually process. These jobs are pending input service, and are processed when buffers become available.
lowest
Specifies a number within the range 1 to 999999 to indicate the lowest job number. This number must be at least 17 job numbers lower than the value of ‘highest’ in the range.
highest
Specifies a number within the range 18 to 999999 to indicate the highest job number. This number must be at least 17 job numbers higher than the value of ‘lowest’ in the range.
joblim
Specifies the maximum number of jobs that may be in the JES3 complex at any given time (within the range 1 to 999999).
JES3 uses as the actual job maximum the smaller of the following values:
  • The joblim value
  • The value obtained by the calculation: highest – lowest + 1
  • The number of job control table (JCT) entries that will fit in the JCT data set (z/OS JES3 Initialization and Tuning Guide provides information about how to determine this number).

If you lower the upper end of the job number range or increase the lower end of the job number, jobs that are in the system and were previously assigned job numbers outside the new range are lost. For example, assume you have specified 1-50 as the range of job numbers and JES3 has assigned numbers 1-35. You now change the range of job numbers to 1-30. Jobs with numbers 31-35 will be lost.

There is a way to avoid losing jobs when you change the upper end of the range using a warm start. Before making the change, execute the dump job (DJ) facility to save jobs that are in the job queue. After the change, again execute the dump job facility to restore these jobs to the job queue. See z/OS JES3 Commands for information about using the dump job facility.

JOBTRACK
Indicates the scope of ENF 70 events:
SYSPLEX
Specifies that ENF 70 events are signaled to listeners across all systems in the SYSPLEX. This is the default.
JGLOBAL
Specifies that ENF 70 events are signaled only to listeners on the JES3 Global.
OFF
Disables signaling of ENF 70 events.
If you specify a subparameter that is not valid, JES3 uses the parameter default (SYSPLEX).
MT=
Indicates whether JES3 is to turn the writer output multitasking facility on or off. To determine whether to turn the facility on or off, see the topic “Using the Writer Output Multitasking Facility” in z/OS JES3 Initialization and Tuning Guide.
ON
Requests that JES3 enable the writer output multitasking facility. Specify ON only when the global is a multiprocessor.
OFF
Requests that JES3 turn off (disable) the writer output multitasking facility. Specify OFF when the global is a uniprocessor.

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

MT=
Indicates whether JES3 is to turn the writer output multitasking facility on or off. To determine whether to turn the facility on or off, see the topic “Using the Writer Output Multitasking Facility” in z/OS JES3 Initialization and Tuning Guide.
ON
Requests that JES3 enable the writer output multitasking facility. Specify ON only when the global is a multiprocessor.
OFF
Requests that JES3 turn off (disable) the writer output multitasking facility. Specify OFF when the global is a uniprocessor.

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

MT=
Indicates whether JES3 is to turn the writer output multitasking facility on or off. To determine whether to turn the facility on or off, see the topic “Using the Writer Output Multitasking Facility” in z/OS JES3 Initialization and Tuning Guide.
ON
Requests that JES3 enable the writer output multitasking facility. Specify ON only when the global is a multiprocessor.
OFF
Requests that JES3 turn off (disable) the writer output multitasking facility. Specify OFF when the global is a uniprocessor.

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

SE=
Specifies the maximum number of scheduler elements (SEs) that may be constructed for any job. The value chosen should equal the number of scheduler elements required to support the largest job (in terms of SEs) to be run in the complex. A number between 10 and 90 may be specified. This specification is used to calculate the maximum size for a JCT and its SEs (JCT record size).
XCFGRPNM=
Each complex in a sysplex is required to use a unique XCF groupname. The groupname must follow all XCF naming conventions. It must be 1-8 alphanumeric characters including $, # and @. The default is the node name defined on the NAME= keyword on the NJERMT initialization statement for the home node (HOME=YES specified), if one exists. It is recommended that the default be used unless it conflicts with an existing XCF groupname, or your home node name is not a valid XCF group name. This default takes effect only during a warm or a cold start. During a hot start with refresh, if the home definition is changed, the value of XCFGRPNM from the last warm or cold start remains in effect.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014