OPS/MVS Health Checker process questions.
Release : 14.0
“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.
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.