Message flood prevention using the OPS4402O message rule

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

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.

 

Environment

Release: ALL

Resolution

Utilize the OPS/MVS parms MSGTHRESHOLD/MSGDRAINRATE to identify possible 'problem' jobs, specifically those generating excess message traffic. Review the sample rule OPS4402O in hlq.CCLXRULS which will serve as a template to fire on these conditions. This sample simply generates an alert, but more robust logic such as creating a dynamic MSG rule to suppress/delete future message traffic from the offending ASID or cancelling the job altogether can be added.

Note: The CONSOLE ASID may also trigger the OPS4402O message as fallout from messages issued by the offending job. Precautions should be taken to only process the job that is the source of the excess messages being generated.

Additional Information