How can I create effective OPS/MVS automation to monitor and respond to a potential WTO message flood condition caused by a problem ASID? We would like to implement a solution to catch these situations before they get to the point where the WTO message queue is almost full. We would like a solution that could potentially be universal for any started task.
We recommend utilizing the OPS/MVS parms MSGTHRESHOLD/MSGDRAINRATE to identify possible 'problem' jobs specifically, if some ASID is spitting out a lot of message traffic. Have a look at the sample rule OPS4402O in hlq.CCLXRULS for ideas of a rule to fire on these conditions. This sample simply generates an alert, but more robust logic (creating dynamic MSG rule to suppress/delete future message traffic from ASID) can be added.
Address Space Message Rate Control.
Available Sample Rules