To establish an interface between CA OPS/MVS and OMEGAMON, insert an OxREPORT DD statement in the OMEGAMON JCL procedure that uses the SUBSYS keyword to identify CA OPS/MVS as the target of that file.
SEND OMEGAMON MVS EXCEPTIONS TO CA OPS/MVS //OMREPORT DD SUBSYS=(OPSS,OMEGAMON,MVS), // DCB=(RECFM=FBA,LRECL=81,BLKSIZE=81) SEND OMEGAMON CICS EXCEPTIONS TO CA OPS/MVS //OCREPORT DD SUBSYS=(OPSS,OMEGAMON,CICS), // DCB=(RECFM=FBA,LRECL=81,BLKSIZE=81) SEND OMEGAMON CICS EXCEPTIONS TO CA OPS/MVS; IDENTIFY SOURCE CICS SYSTEM //OCREPORT DD SUBSYS=(OPSS,OMEGAMON,CICS,CICSTEST), // DCB=(RECFM=FBA,LRECL=81,BLKSIZE=81) SEND OMEGAMON IMS EXCEPTIONS TO CA OPS/MVS //OIREPORT DD SUBSYS=(OPSS,OMEGAMON,IMS), // DCB=(RECFM=FBA,LRECL=81,BLKSIZE=81) SEND OMEGAMON DB2 EXCEPTIONS TO CA OPS/MVS //ODREPORT DD SUBSYS=(OPSS,OMEGAMON,DB2), // DCB=(RECFM=FBA,LRECL=81,BLKSIZE=81)
The format for the JCL examples above is as follows:
//ddname DD SUBSYS =(ssid,OMEGAMON,type{,reportid})
Specifies the ddname associated with the file.
Specifies the four-character CA OPS/MVS subsystem ID to which these messages are routed (usually OPSS).
Identifies the specific Tivoli OMEGAMON XE on z/OS product. The type must be MVS, CICS, IMS, or DB2.
(Optional) Specifies a unique report ID you can use in a rule to identify the source of the message.
Copyright © 2014 CA Technologies.
All rights reserved.
|
|