Capturing messages from Omegamon Alerts in OPS/MVS

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

I am trying to determine the best way to capture alerts that are generated from Omegamon.

 

In syslog the alert looks like this

SEND 'OMMV003W XXXX XXXXXX IS NOW SOFT CAPPED'

 

I then go into OPS ISPF application 7.2 and there is no OMMV003W is in the list.

Since I do not see it listed, I am not sure if OPS/MVS can see the message id OMMV03W in the SEND statement.

Cause

The Omegamon alert is sent in an unusual format with the first word being SEND rather than the normal messageID

Resolution

OPS/MVS can see and respond to the OMEGAMON Alert.   However, since the alert comes in the form of SEND 'OMMV003W XXXX XXXXXX IS NOW SOFT CAPPED' rather than just 'OMMV003W XXXX XXXXXX IS NOW SOFT CAPPED', the alert has to be coded on the SEND instead of the message ID as normally done.   It would look similar to:

  )MSG SEND                                    
   )PROC                                        
   if pos('OMMV003W',msg.text) > 0 then         
       do                                       
       /*<-- put your actions here -> */        
       end                                      

In the Automation Analyzer (=7.2) the following settings would need to be set in order to see the SEND in the Message Identifier column.