Interactions between MainView AutoOPERATOR and IBM IBM MQ

The diagrams in this section illustrate the relationships between the components of MainView AutoOPERATOR and both z/OS and distributed queue managers.

The following figure shows the interaction between MainView AutoOPERATOR and a z/OS queue manager.

MainView AutoOPERATOR is connected to a IBM MQ queue manager, which it listens to for instrumentation events and nonevent messages. If the instrumentation event or nonevent message is set to trigger a Rule for that event, the Rule can perform one or more of the following actions:

• Create an ALERT or journal message
• Launch an EXEC
• Issue a IBM MQ command to manipulate IBM MQ objects and attributes

If the Rule issues an ALERT, the ALERT is sent to an operator who performs the appropriate action. A journal message is also logged in the BBI Journal, which contains messages about the queue manager and queues.

If an EXEC is launched, it can create an ALERT, issue a IBM MQ command to alter a IBM MQ object or attribute, or get and put messages directly using the MQI. The EXEC may also log a message to the BBI Journal.

If the Rule or the EXEC issues a IBM MQ command, the IBM MQ objects and attributes can be modified to resolve the issue that initially triggered the MQS event.

The following figure illustrates the relationship between MainView AutoOPERATOR and both an IBM z/OS and distributed (remote) queue manager.

MainView AutoOPERATOR interacts with a distributed queue manager in the following ways:

• The distributed queue manager sends its instrumentation events and nonevent messages through the z/OS queue manager to be listened to by MainView AutoOPERATOR.
• MainView AutoOPERATOR Rules and EXECs can send queue manager commands to the distributed queue manager in response to these messages and events.
• MainView AutoOPERATOR Rules or EXECs can issue a PCF (Programmable Command Format) command to manipulate the IBM MQ objects and attributes in the distributed queue manager.