We recently implemented SRDF/A with our 2 DMX4s between CA and TX.  This first implementation is for our 2 z/OS mainframes one in TX and one in CA.  During normal processing we have no problem keeping 30 second cycles. During heavy batch processing our cycles can elongate to 60 minutes or more. When we get too far behind SRDF uses too much cache and sometimes we drop.  I am trying to use ECC to monitor SRDF.  There is an alarm set up to send an alert if we get a certain wp_limit drop. We got a wp_limit drop during month end but did not get the aleret.  It turns out there is a second condition that can trigger a slightly different wp_limit drop and it has its own alert that needs to be set.  I'm concerned that some day we will drop with some new condition that is not caught by our currenn ECC alerts.

Is there a better way of monitoring SRDF/A, maybe outside of ECC.  Maybe the mainframe could check something to make sure it is still up and alert if it is down.  I am an Open Systems (Solutions Enabler etc) but I have become familiar with some of the mainframe SQ Query commands etc.