|
- Description:
- Looks at the slot usage of each local page data set. The check
generates an exception if the usage on any data set meets or exceeds the warning threshold.
- Reason for check:
- To maximize the efficiency of ASM slot management, you should
keep the slot usage on all local page data sets below 30% .
- z/OS® releases the check
applies to:
- z/OS V1R8 and later.
- User override of IBM® values:
- The following shows the default keywords for the check, which
you can override on either a POLICY statement in the HZSPRMxx parmlib
member or on a MODIFY command. This statement may be copied and modified
to override the check defaults:
UPDATE,
CHECK(IBMASM,ASM_LOCAL_SLOT_USAGE),
INTERVAL(00:30),
SEVERITY(MED),
PARM('THRESHOLD(30%)'),
DATE('date_of_the_change')
- Debug support:
- No
- Verbose support:
- No
- Parameters accepted:
- Yes, as follows:
- When not using dynamic severity: THRESHOLD(value),
- When using dynamic severity: THRESHOLD_HIGH(value),
THRESHOLD_MED(value), THRESHOLD_LOW(value),
THRESHOLD_NONE(value)
Note that the thresholds specified should
increase in value as the severity increases, since a higher value indicates a more severe condition
(higher usage of the paging data set), as shown in the following example:
PARM('THRESHOLD_HIGH(80%),THRESHOLD_MED(60%), THRESHOLD_LOW(30%)')
The variable for the parameters is as follows: - value
- An integer, 0-100 indicating the warning threshold percent. It
may optionally be followed by %.
Default: THRESHOLD(30%)You can use synonyms
for these parameters, as follows: Parameter |
Synonyms |
---|
THRESHOLD_HIGH |
|
THRESHOLD_MED |
|
THRESHOLD_LOW |
|
THRESHOLD_NONE |
|
PARM('THRESHOLD_HIGH(60%),THRESHOLD_MED(25%)')
- Reference:
- For information on auxiliary storage management initialization,
see z/OS MVS Initialization and Tuning Guide .
- Messages:
- This check issues the following exception messages:
See the ILRH messages in z/OS MVS System Messages, Vol 9 (IGF-IWM).
- SECLABEL recommended for multilevel security users:
- SYSLOW - see z/OS Planning for Multilevel Security and the Common Criteria for
information on using SECLABELs.
|