Automate messages recorded in SYSOUTs or datasets instead of being issued as console messages in OPS/MVS

Products

• OPS/MVS Event Management & Automation

Issue/Introduction

Sometimes it is necessary to automate messages that are directed to SYSOUTs or datasets by a job or started task. If those messages are not sent WTO to a z/OS console the OPS/MVS AOF component is not going to be able to record them in the OPSLOG and take actions upon them via AOF rules.

How to automate messages using OPS/MVS that are recorded in SYSOUTs or datasets instead of issued as console messages?

 

Environment

 

Resolution

Use the OPS/MVS Generic Dataset Interface (GDI) to direct output from SYSOUTs or datasets such as log files to OPS/MVS for processing by the AOF component.

 

To establish a generic data set interface with OPS/MVS, provide JCL statements that identifies OPS/MVS as a target for the output.  The syntax is as follows: 

                      //ddname DD SUBSYS =(ssid,OPSDSN{,color}{,reportid}{,posmgid})

- The only required parameters are ssid (the OPS/MVS subsystem id) and “OPSDSN” which has to be specified as is.

             For Example:    //CPERROR   DD SUBSYS=(OPSS,OPSDSN,,,CPMSG) 

            - The above statement sends messages from the DD CPERROR to the OPSS subsystem with a message id of “CPMSG”.

- The last parameter (posmgid) can also be expressed as a number meaning the numeric starting position in the text of each record at which OPS/MVS is to begin its scan for a message ID.