The SCHED statements are described as follows:
MT SIZE{(nnnK)}
{(NONE)}
{(24K) }
- Specifies
the size (in kilobytes) of the master trace table, which is used by
the TRACE command. The system creates the master trace table during
master scheduler initialization. By default, the master trace table
is 24 kilobytes in size.
To specify a different size for the master
trace table, specify MT SIZE(nnnK), where nnn is any value from 16 to 999. You must add
the letter ‘K’ for the increments (kilobytes), and enclose the entire
value in parentheses.
For example, to have the system create
a master trace table of 50 kilobytes, specify the following MT statement
in SCHEDxx:
MT SIZE(50K)
If you do
not want a master trace table to be created, specify
MT
SIZE as
(NONE), as follows:
MT SIZE(NONE)
No table is created.
If you specify more than one MT statement in a SCHEDxx member, the
system will use the first occurrence and ignore any subsequent MT
statements.
Default: MT SIZE(24K)
- NORESTART CODES(code,code...)
- Specifies
which system and user abend codes are to be deleted from the table
of abend codes that are eligible for automatic restart.
RESTART
and NORESTART allows the installation to customize the list of abend
codes that are eligible for automatic restart. This list is created
by merging the user abend codes specified on the RESTART statement
with the list of IBM-supplied system abend codes. A user abend code
cannot have the same number as a system abend code. The system will
ignore a user abend code that is a duplicate of a system abend code.
The IBM-supplied system abend codes are listed in
Table 1.
Table 1. IBM-supplied system abend codesCode |
Code |
Code |
Code |
001 |
20A |
422 |
813 |
031 |
213 |
513 |
837 |
033 |
214 |
514 |
906 |
03A |
217 |
613 |
913 |
0A3 |
2F3 |
614 |
926 |
0B0 |
313 |
626 |
937 |
0F3 |
314 |
637 |
A14 |
100 |
317 |
700 |
B14 |
106 |
32D |
714 |
B37 |
113 |
413 |
717 |
C13 |
117 |
414 |
737 |
E1F |
137 |
417 |
806 |
E37 |
Value Range: 0-FFF (Hex)
- RESTART CODES(code,code...)
- Specifies the
user abend codes that are to be eligible for automatic restart. These
are to be added to the system abend codes that are supplied by IBM®.
Value Range: 0-FFF
(Hex)
- PPT
- Allows the installation
to specify a list of programs that require special attributes. Sometimes,
your application programs will need to possess special properties
to run as efficiently and securely as possible. For example, an application
that requires access to fetch-protected system data will need a system
key (0-7) instead of the usual problem program key of 8. Or, for example,
an application that cannot run V=R, but must not be swapped out because
of real-time considerations, will need to be identified to the system
as nonswappable. Entries for these programs are created in the program
properties table (PPT).
- PGMNAME(name)
- PGMNAME(name) identifies by name the program, specified in the
PGM parameter on the EXEC statement for a job or step, that requires
special attributes. It must consist of an alphabetic or national (#,
@, or $) character followed by 0 to 7 alphanumeric or national characters.
PGMNAME(name)is required on the PPT statement. A program specified
in the PPT will obtain special attributes only if all of the following
are true:
- The program is fetched from an authorized library
or from the link pack area (pageable, modified, fixed, or dynamic
LPA).
- All STEPLIB data sets are authorized if a STEPLIB DD (or concatenation)
exist for the step.
- All JOBLIB data sets are authorized if a JOBLIB DD (or concatenation)
exists for this job and no STEPLIB DD exists for this step.
Otherwise, problem program attributes are assigned. All programs described by PPT entries must come from
an APF library or concatenation, or from the link pack area.
Note: - To override an IBM-supplied entry in the PPT, use the same program
name as the IBM-supplied entry.
- Although you cannot remove entries from the PPT, you can create
the effect of removing an entry from the PPT by specifying the program
name without special attributes.
For example, a JES2 installation
might (for auditing purposes) want to “remove’ the IATINTK entry from
the PPT by including the following statement in the SCHEDxx member:
PPT PGMNAME(IATINTK)
This statement
overrides the existing IATINTK entry in the PPT, and causes any APF-authorized
program named IATINTK to run with the same attributes as a problem
program.
- If you specify more than one PPT statement with the same program
name, the systems accepts only the first occurrence of the name and
issues error message IEF732I for all subsequent occurrences of that
name.
- When referring to a DD statement, the system does not honor requests
for special properties as defined in the PPT.
Default: NONE
- {CANCEL}|{NOCANCEL}
- The program specified on PGMNAME can be canceled (CANCEL) or cannot
be canceled (NOCANCEL).
Default: CANCEL
- KEY(n)
- The program specified on PGMNAME is to have the protection key
(n) assigned to it. The range of values for n is 0 through 15. A KEY
value greater than 8 requires special consideration. Usually, keys
greater than 8 are reserved for V=R programs, and the system assigns
these keys dynamically. If the KEY field is specified for a V=R program,
ensure that no other V=R program runs at the same time with the same
key. A V=V program may run with a KEY value greater than 8 when V=R
programs are running with channel program translation.
Value Range: 0-15
Default: Key 8
- {SWAP}|{NOSWAP}
- The program specified on PGMNAME is swappable (SWAP) or non-swappable
(NOSWAP).
Default: SWAP
- {PRIV | NOPRIV}
- The program specified on PGMNAME is privileged (PRIV),
or not privileged (NOPRIV).
A task marked PRIV is put
in the SYSSTC service class if it is not explicitly classified in
the WLM classification rules.
Default: NOPRIV
- {DSI | NODSI}
- The program specified on PGMNAME requires data set
integrity (DSI) or does not require data set integrity (NODSI). Data
set integrity means that the job holds an ENQ for the data sets it
allocates. The DSI/NODSI option applies to batch allocation only.
Dynamic allocation uses its input parameters to determine whether
to enqueue on data sets. JES2 is an exception in that it honors the
PPT specifications and uses DSI/NODSI for dynamic allocations of the
JES2 PROCLIB data sets.
If DSI is specified, the system acquires
an ENQ for all data sets requested by the program. The ENQ is exclusive
or shared, depending on the disposition on the DD request.
If NODSI is specified, the system still issues an ENQ for all data
sets requested by the program. However, the ENQ is released before
the problem program is started.
Jobs for which NODSI is specified
are not started if the job contains either a JOBLIB or STEPLIB, and
both of the following conditions are true:
- The job cannot get the ENQ on the following types of data set
names:
- GDG absolute generation data set name (unless the absolute generation
data set name is specified on the JCL).
- Real data set name (when its corresponding alias data set name
is specified on the DD statement in the JCL).
- The installation has specified WAITALLOC(NO) on the SDSN_WAIT
keyword in the ALLOCxx member of SYS1.PARMLIB, or has taken the default.
For more information about the SDSN_WAIT keyword, see ALLOCxx (allocation system defaults).
Note: - For NODSI, the job must be a one-step job. If the job is not a
one-step job, NODSI is nullified and the system issues message IEF188I.
All other properties remain in effect.
- NODSI is not honored for jobs that use unauthorized JOBLIBs or
STEPLIBs. The system assumes DSI for these jobs.
Default: DSI
- {PASS| NOPASS}
- The program specified on PGMNAME can or cannot bypass security
protection (password protection and RACF®). PASS indicates that security protection is in effect;
NOPASS indicates that security protection is not required. PASS is
the default.
Jobs that request the bypass-security-protection
property will receive the property. However, a protected data set
cannot be deleted via JCL (that is, by coding a disposition of DELETE)
without the password. This is because the bypass-security-protection
property is turned off when the job enters deallocation processing.
Note that the NOPASS parameter option does not
apply to the STEPLIB or JOBLIB DD from which the named program is
to be fetched, and that the address space in which the program is
executing must have the security access required to open the JOBLIB
or STEPLIB dataset.
Default: PASS
- {SYST | NOSYST}
- The program specified on PGMNAME is a system task and is not timed
(SYST) or is not a system task and is to be timed (NOSYST). For SYST,
the program must be a one-step job started by a START or MOUNT command.
If these conditions are not met, SYST is nullified and the system
issues message IEF188I. All other properties remain in effect.
If procedures are multistep or if NOSYST is specified, TIME=1440
may be required to prevent timeout.
In goal mode,
a task marked SYST is put in the SYSSTC service class unless it is
explicitly classified in the WLM classification rules before any SPM
rule entries.
Default: NOSYST
- SPREF
- The program specified on PGMNAME must have all private area short-term
fixed pages assigned to preferred (nonreconfigurable and non-V=R)
storage frames.
Default: None
- LPREF
- The program specified on PGMNAME must have all private area long-term
fixed pages assigned to preferred (nonreconfigurable and non-V=R)
storage frames.
Default: None
- NOPREF
- The program specified on PGMNAME does not need to have all private
area short-term fixed pages assigned to preferred storage frames. That
is, the program's short-term fixes are in fact short-term fixes and
can be allowed in reconfigurable storage.
Default: None
Notes on using SPREF, LPREF, and NOPREF: - LPREF is meaningless for programs that issue SYSEVENT TRANSWAP
to become nonswappable.
- Use of SPREF, LPREF, and NOPREF forces the program's private area
fixed pages and LSQA pages into preferred storage frames, thus ensuring
that they will not prevent taking storage offline.
- Use SPREF, LPREF, or NOPREF for programs whose fixed pages could
prevent the successful execution of a VARY STOR,OFFLINE command (or
could fragment the V=R area) if they were
assigned frames in reconfigurable or V=R storage.
- SPREF and LPREF are significant for swappable programs(SWAP) that
have a special requirement for preferred frames.
- SPREF and LPREF are intended for use with authorized swappable
programs that issue SYSEVENT DONTSWAP to become nonswappable for short
periods (rather than using NOSWAP).
- SPREF and LPREF should be specified when the preferred storage
requirements for a nonswappable program are unknown. This will ensure
that all fix requests and LSQA requests will get preferred storage.
- NOPREF is significant only for users of the SYSEVENT TRANSWAP.
This includes V=R job steps, nonswappable programs, applications using
the BTAM OPEN function, and any applications using a system function
that issues SYSEVENT TRANSWAP.
- For an application program that issues SYSEVENT DONTSWAP, or issues
SYSEVENT REQSWAP followed by a SYSEVENT DONTSWAP, do one of
the following:
- List the program in the PPT and specify SPREF and LPREF.
This
allows the program to be attached as swappable, but all LSQA and private
area fixed pages will be assigned preferred frames during the entire
job step.
- Remove SYSEVENTs REQSWAP and DONTSWAP from the program. List
the program in the PPT as nonswappable (NOSWAP) and do not specify
NOPREF.
This allows the program to be attached as nonswappable,
and all LSQA and private area fixed pages will be assigned preferred
frames during the entire job step.
- An I/O device requiring operator intervention can interfere with
taking storage offline by fixing pages in reconfigurable storage.
For example, a printer requiring action to be taken, or a tape unit
with a mount pending. Until the required action is completed, the
storage associated with the I/O operation cannot be taken offline.
This problem cannot be bypassed by using SPREF, LPREF, or NOPREF.
- {HONORIEFUSIREGION} | {NOHONORIEFUSIREGION}
- When HONORIEFUSIREGION is specified, region and MEMLIMIT settings
specified through, or otherwise affected by the IEFUSI exit take effect.
When NOHONORIEFUSIREGION is specified, region and MEMLIMIT values
specified through, or otherwise affected by the IEFUSI exit are ignored.
In other words, when NOHONORIEFUSIREGION is specified for a program,
MEMLIMIT values or limits cannot be altered through the IEFUSI exit.
This PPT attribute is used to bypass IEFUSI region controls for specific
programs that require a larger than normal region in order to successfully
execute.
For more information about controlling region size
and region limits using the IEFUSI exit, see z/OS MVS Initialization and Tuning Guide.
Default: HONORIEFUSIREGION
- {CRITICALPAGING} |{NOCRITICALPAGING}
- The program specified on PGMNAME owns storage that is critical or
is not critical for Hyperswap operation. CRITICALPAGING indicates
that the storage associated with the program specified on PGMNAME
is critical for Hyperswap operation. Therefore, storage management
should never page out this storage if possible. NOCRITICALPAGING
(the default) indicates that the storage associated with the program
specified on PGMNAME is not critical for Hyperswap operation and can
be paged out at any time.
Note: - IBM Supplied PPT entries
marked CRITICALPAGING cannot be overridden.
- Use this parameter in conjunction with the CRITICALPAGING switch
to increase the likelihood of a successful HyperSwap® operation. (See the FUNCTIONS
statement of COUPLExx.)
Default: NOCRITICALPAGING