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


RRS_Storage_NumServerReqs

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

Description:
Monitor the level of virtual storage usage in the RRS address space to prevent a terminating failure.
Reason for check:
If the count of server requests within RRS grows too big then RRS might be encountering a hang situation.
z/OS® releases the check applies to:
z/OS V1R7 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(IBMRRS,RRS_STORAGE_NUMSERVERREQS)
    ACTIVE
    SEVERITY(HI),INTERVAL(0:05),DATE('date_of_the_change')
    REASON('Your reason for making the update.')
Parameters accepted:
No
Debug support:
No
Verbose support:
No
Reference:
For more information, see z/OS MVS Programming: Resource Recovery.
Messages:
This check issues the following exception messages:
  • ATRH016E
See the ATRH messages in z/OS MVS System Messages, Vol 3 (ASB-BPX).
SECLABEL recommended for multilevel security users:
SYSLOW - see z/OS Planning for Multilevel Security and the Common Criteria for information on using SECLABELs.
Ouptut:
ATR016E The current number of server task requests in RRS is
curreqs which exceeds the threshold
 
Explanation: The number of server task requests in RRS has
exceeded the manageable threshold and could be an indication of
a potential problem in RRS.  Please monitor the level of
activity in RRS and the associated resource managers and see if
anything indicates a slow down or complete halt to transaction
processing.
 
System Program Response:
Use the available RRS data collection techniques (panels,
console display command, or batch program) to assess the level
of transaction activity in RRS and determine if it is unusual or
unexpected.
 
If the level of activity is determined to be a problem then use
the data collection methods to determine if it is a problem with
a specific work manager then check with that work manager
function for problems.

Go to the previous page Go to the next page




Copyright IBM Corporation 1990, 2014