Automate IBM MQ events with BMC AMI Ops Automation Rules

This section describes how 

BMC AMI OpsA

 automates IBM MQ events, and how to create rules for event messages and nonevent messages.

How BMC AMI OpsA automates IBM MQ events

BMC AMI OpsA uses Rules to perform automation for various system events such as z/OS messages, commands, and ALERTs.

Rules can also be used to provide automated responses to IBM MQ events. This section describes important concepts about BMC AMI OpsA Rules and IBM MQ events.

BMC AMI OpsA Rules

A Rule is a two-part statement: when the conditions of the first part of the statement are met (the selection criteria), the automation actions specified in the second part are performed.

When BMC AMI OpsA is installed, you can create Rules that provide automated actions such as issuing commands, creating ALERTs, or rerouting messages in response to IBM z/OS system events. BMC AMI OpsA Rules listen for these events. When the event occurs, the Rule fires and the automation action is taken.

When the BMC AMI Ops Automation for MQ component is installed, you can create Rules for IBM MQ events. The IBM MQ events can originate either from queues within z/OS or from distributed platforms. BMC AMI OpsA listens for IBM MQ messages and recognizes them as event type MQS. Enabled Rules listen for these MQS messages and when the conditions of the Rule are met, the Rule fires to provide automated responses to the message.

Important

For BMC AMI Ops Automation for MQ to listen for and automate events from distributed queue managers (such as those running on Microsoft Windows, UNIX, or IBM OS/2, or OS/400 operating systems), you must define connectivity and activate communications between z/OS and distributed queue managers as described in Defining-connectivity.

This section contains the following topics:


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*