OPS/MVS Health Checker process questions

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

OPS/MVS Health Checker process questions.

1. About below check profile against OSF queue depth.  We found that the value reported in the IBM health checker is different to the value displayed in ‘Maximum OSF Execute Queue Depth’ value under OPSVIEW =4.3 panel.  Would Broadcom please advise what’s the value and how’s the value is being obtained are being used for calculation against the defined OSFTSLQUE, OSFQUE, OSFTSPQUE, and USSQUE value?   
   OPSMVS_TSLMAXQUSG
   OPSMVS_TSOMAXQUSG
   OPSMVS_TSPMAXQUSG
   OPSMVS_USSMAXQUSG
2. Will there be any high watermark continuous alerting issue?

 

Environment

Release : 14.0

Resolution

Answer:

1. In the health check, there’s the message like -- 

        “The maximum number of commands that have been on the OSF TSO queue is …”.                                                    

        For this message, the max queue depth during last health check interval is used."   

        So the health check message "“The maximum number of commands that have been on the OSF TSO queue is …”                                                                                                                  is of accurate description if you take the health check interval into consideration.           

        For OPS lifetime high value of the queue depth, please refer back to OPSVIEW 4.3, not the Health checker. 

   2. No, since it’s not looking at the historical maximum OSF server queue depth which is not resettable, unless the current queue                                                                                                 depth goes over the threshold every time the health check runs.

 

In conclusion,

The health check message “The maximum number of commands that have been on the OSF TSO queue is …”  is an accurate description since it works with the health check interval. 

It's the high value during the last interval. The value will be updated for each interval. It's not the OPS lifetime maximum as shown in OPSVIEW 4.3. 

There should NOT be any high watermark continuous alerting issue.