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.

If not a work manager problem then use the data collection methods to determine if it is a problem with a specific resource manager.

If it appears to be neither a specific work manager nor a specific resource manager problem then monitor RRS using this health check until either the exception is resolved or the count continues to grow. You can use the following command to change the timing of the check F HZSPROC,UPDATE,CHECK=(IBMRRS,RRS_STORAGE_NUMTRANS),INTERVAL=hh:mm

where 'hh' is the number of hours and 'mm' the number of minutes that should be used at the timing interval for the check.

If it is an RRS problem then take a dump of the RRS address space and report the situation to IBM® service.

The other possibility is that this level of activity is not unusual for the workload on this system in which case you can use the following command to change the threshold level for this check.

F HZSPROC,UPDATE,CHECK=(IBMRRS,RRS_STORAGE_NUMTRANS),parm=xxxx

where 'xxxx' is the number to be used as the threshold for the check.

In this case the HZSPRMxx parmlib for the RRS checks should be updated similarly (the RRS default checks are in ATRHZS00 in SAMPLIB).