Multiple lines of a WTO message may appear in the SYSLOG consecutively.
Is it possible to leave only the first (first line) message and prevent the rest of the same message from being output to SYSLOG?
<Message Output Image (before suppression)
00.00.01 Mxxxx1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
00.00.02 Mxxxx1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
00.00.03 Mxxxx1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
<Message output image (after suppressed)
00.00.01 Mxxxx1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
OS : z/OS
Product : OPS/MVS Event Management & Automation
Release : All
Component : OPSMVS
It is possible to suppress the same message output continuously within a certain period of time.
With the OPSTHRSH function it's easily creating criteria threshold automation logic within an AOF rules which can fire numerous times within a specific time interval.
For example, threshold automation could cause a particular function of automation to take place if an event occurs x times in y minutes.
Of the message events that occur within a certain time period, only the first message output to SYSLOG is retained, and the second and subsequent duplicate messages can be prevented from being output to SYSLOG.
Specifically, use OPSTHRSH type E.
<Reference>
Sample of a case where multiple Mxxxx1 messages are displayed at 20-second intervals.
Only the first Mxxxx1 message will be displayed in SYSLOG.
The second and subsequent Mxxxx1 messages will be suppressed from the console and SYSLOG, but will continue to appear in OPSLOG.
After 20 seconds, if a new Mxxxx1 message appears, the
The message rule is activated.
As a result, the SYSLOG will continue to display only one identical message within 20 seconds, regardless of the number of messages output.
)MSG Mxxxx1
)PROC
count = OPSTHRSH('E','20')
if count > 1 then return delete
:
If there is a rule involving Mxxxx1 messages, code it here.
:
return
For more information, see the OPSTHRSH Function in OPS/MVS documentation.