Event Management › Integration with External Event Collection Systems › CA OPS/MVS Interface

CA OPS/MVS Interface

To simplify CA Automation Point message-handling, we recommend that you use a mainframe-based automation product, such as CA OPS/MVS, to perform the following tasks:

• Limit much of the message traffic to the master console by either suppressing a message entirely or using route codes to limit the number of consoles displaying the message. This is especially important for highlighted messages.
• Monitor the status of the WTO buffers and clear the buffers if they begin to fill up. Sample rules are available for CA OPS/MVS for this purpose. (This is not necessary for RCS sessions, because CA Remote Console does not allow the buffers to fill up.)

The CA Automation Point ADDRESS OPS command environment provides the outbound communication to CA OPS/MVS for the interface. The interface lets you perform the following outbound communication tasks:

• Send CA Automation Point messages to CA OPS/MVS
• Execute commands from CA OPS/MVS
• Execute REXX programs or TSO commands under an OSF TSO server on a CA OPS/MVS system
• Return a list of CA OPS/MVS systems currently defined to CA Automation Point with their current status

The CA Automation Point to CA OPS/MVS Interface also supports inbound communication from CA OPS/MVS. Using this interface, you can initiate the following tasks from CA OPS/MVS:

• Send WTO messages directly to CA Automation Point rules processing
• Invoke REXX programs on the CA Automation Point workstation
• Trigger NMFIND (notification) requests
• Issue PPQ WRITE commands from CA Automation Point