ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

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

book

Article ID: 41336

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

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 WTOed to a z/OS console the CA OPS/MVS AOF component is not going to be able to record them in the OPSLOG and take actions upon them via AOf rules.

Question: 

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

Answer: 

The CA OPS/MVS Generic Dataset Interface (GDI) can be used for this purpose. Using this interface you can direct output from SYSOUTs or datasets such as log files to CA OPS/MVS for processing by the AOF component.

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

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

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

Example:

//CPERROR   DD SUBSYS=(OPSS,OPSDSN,,,CPMSG) 

The above statement sends messages from the DD CPERROR to the CA OPS/MVS subsystem OPSS 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 CA OPS/MVS is to begin its scan for a message ID.

Additional Information:

For more information about this interface visit the following link: CA Technologies Documentation

Environment

Release: PVLA2.00200-12.2-OPS/MVS-Event Management & Automation-for JES2
Component: