Advanced Topics › CA OPS/MVS Considerations › Message Presentation to CA OPS/MVS

Message Presentation to CA OPS/MVS

CA MIC-imported messages are directed from the local CA MIC subsystem to the local CA OPS/MVS subsystem using standard Subsystem Interface protocols. Certain WQE control block fields for imported messages are altered by the CA MIC subsystem before presentation to the CA OPS/MVS subsystem. These processes allow the local CA OPS/MVS subsystem to determine that a given message came from the CA MIC subsystem, and that the message originated on an external system. The CA MIC subsystem changes the following WQE control block fields:

• The WQERISS bit in the WQEFLG1 field is set to ON.
• The WQEFORN bit in the WQEFLG2 field is set to ON.
• The WQESYSNM field contains the name of the system from which the message originated.
• The WQEJOBNM field contains the job number of the task that originally issued the message. When the originating task was a z/OS subsystem or a z/VM application that did not have a job number, the OPSLOG column that displays this information shows a value of “NONE”.
• The WQEOJBID field contains the job number of the task that originally issued the message. This field contains the z/OS subsystem name or the z/VM application name when the originating task was an OS subsystem or a z/VM application, which did not have a job number.
• The WQEOJBNM contains the name of the task that originally issued the message.

CA MIC presents imported messages to CA OPS/MVS using these standards regardless of any CA MIC message editing parameter values in effect on any system. In other words, CA MIC consistently presents CA OPS/MVS with original message data regardless of the CA MIC message editing that may have taken place on a given system based on the CA MIC MIMINIT EDITMESSAGE, SYSNAME, SYSTYPE, and JOBID parameters.

When the local CA MIC subsystem is directing imported messages to the local CA OPS/MVS subsystem, it is important that CA OPS/MVS AOF rules compare the MSG.SYNA environmental variable (the origin system name) with the result of the OPSINFO("SYSNAME") function (the local system name) to identify the systems from which messages are originating. Otherwise, CA OPS/MVS rules may misinterpret CA MIC imported messages as being from the local system, which may result in unpredictable actions by the local CA OPS/MVS subsystem.

Several sample CA OPS/MVS AOF rules and message variables are distributed with the CA OPS/MVS product that may be useful to those who want to use this interface. These samples allow imported messages to be colorized and identified in other ways in OPSLOG and to AOF rules. There are also certain CA OPS/MVS operating parameter values that need to be defined properly before this interface can be operational.

Note: For more information about required CA OPS/MVS parameters settings, as well as useful CA OPS/MVS message variables and sample AOF rules that may be of value to those using this interface, see the CA OPS/MVS AOF Rules Guide.