IBM Health Checker for z/OS User's Guide
Previous topic | Next topic | Contents | Contact z/OS | Library | PDF


VSM_SQA_THRESHOLD

IBM Health Checker for z/OS User's Guide
SC23-6843-02

Description:
The current allocation of SQA storage.
Reason for check:
When the current allocation has reached the user-specified or IBM-specified threshold value, an exception message and storage reports are created. The threshold report includes a comparison to high-water marks on the last IPL as well as the amount of the current allocation. The high-water mark is the highest amount of storage allocated since the system was IPLed.

If the threshold is specified as a percentage value (the default), an exception will be issued when the allocation of storage exceeds that threshold. If the threshold is given as a size in bytes, an exception will be issued when the amount of storage remaining is less than the specified size.

z/OS® releases the check applies to:
z/OS V1R4 and later, in both ESA and z/Architecture® modes.
Parameters accepted:
Yes, as follows:
  • Start of changeWhen not using dynamic severity: SQA(sqabytes | sqa%), ESQA(esqabytes | esqa%)End of change
  • When using dynamic severity: Start of change
    • SQA_HIGH(sqabytes | sqan%), SQA_MED(sqabytes | sqan%), SQA_LOW(sqabytes | sqan%), SQA_NONE(sqabytes | sqann%)
    • Start of changeESQA_HIGH(esqabytes | esqa%), ESQA_MED(esqabytes | esqa%), ESQA_LOW(esqabytes | esqa%), ESQA_NONE(esqabytes | esqa%)End of change
    End of change
    Start of changeNote that when specifying percentages for parameter values, the values should increase as the severity increases since the percentage specifies a percent full amount (a larger value indicates a more severe condition), as shown in the following example:
     PARM('SQA_HIGH(95%),SQA_MED(80%),SQA_LOW(60%), ESQA_HIGH(90%),ESQA_MED(70%)')
    However, if you specify bytes for the parameter values, the values should decrease as the severity increases, since the values specify a bytes-remaining amount (a smaller value indicates a more severe condition), as shown in the following example:
    PARM('SQA_HIGH(64K),SQA_MED(256K),ESQA_HIGH(128K), ESQA_LOW(1M)')
    End of change
sqan%
An integer, 0-10000 followed by %, indicating the threshold percent for utilization of SQA below the line.
sqabytes
A size in bytes, with an optional suffix (K,M) indicating the minimum amount of unallocated SQA.
Start of changeesqan%End of change
Start of changeAn integer, 0-10000 followed by %, indicating the threshold percent for utilization of ESQA above the line.End of change
Start of changeesqabytesEnd of change
Start of changeA size in bytes, with optional suffix (K,M) indicating the minimum amount of unallocated ESQA.End of change
Start of changeDefault:End of change SQA(80%),ESQA(80%)
You can use synonyms for these parameters, as follows:
Parameter Synonyms
SQA_HIGH
  • SQA_HI
  • SQA_H
SQA_MED
  • SQA_M
SQA_LOW
  • SQA_L
SQA_NONE
  • SQA_NO
  • SQA_N
ESQA_HIGH Start of change
  • ESQA_HI
  • ESQA_H
End of change
ESQA_MED Start of change
  • ESQA_M
End of change
ESQA_LOW Start of change
  • ESQA_L
End of change
ESQA_NONE Start of change
  • ESQA_NO
  • ESQA_N
End of change
Note that when specifying percentages for parameter values, your number for the HIGH cases is higher than the MED cases, as shown in the following example:
PARM('SQA_HIGH(95%),SQA_MED(80%),SQA_LOW(60%),ECSA_HIGH(90%),ECSA_MED(70%)')
On the other hand, if you specify bytes for the parameter values the values for HIGH cases are lower than those for MED cases, as shown below:
PARM('SQA_HIGH(64K),SQA_MED(256K),ECSA_HIGH(128K),ECSA_LOW(1M)')
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(IBMVSM,VSM_SQA_THRESHOLD),
INTERVAL(00:15),
SEVERITY(MED),
PARM('SQA(80%),ESQA(80%)'),
DATE('date_of_the_change')
Reference:
For more information, see z/OS MVS Initialization and Tuning Reference.
Messages:
This check issues the following exception messages:
  • IGVH100E
See the IGVH 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.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014