Newer version of documentation BMC provides a newer version of the documentation for this version of the product. As a result, BMC no longer accepts comments in this space.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see bao8301.

Enabling MQS events

Each MQS event falls into a category of events that must be enabled within the queue manager before 

BMC AMI Ops Automation

 Rules can hear them.

Refer to the IBM documentation IBM MQ Script (MQSC) Command Reference for information about enabling these categories. During BMC AMI Ops Automation for MQ initialization, warning messages can be issued for each event category that is not enabled, or BMC AMI OpsA can enable them automatically.

To enable MQS events so that BMC AMI OpsA Rules can hear them, ensure that the BBPARM member AAOMQLxx lists the names of all the queues for which you want to hear events. The event queues must also be defined with the appropriate attributes as described in Customizing-BMC-AMI-Ops-Automation-for-MQ.

For information about listing the queue names in AAOMQLxx, refer to Specifying-queues.

Note

If you use the default AAOMQLxx member, BMC AMI OpsA listens for only MQFMT_EVENT messages that originate from administration queues such as the SYSTEM.ADMIN.QMGR.EVENT, SYSTEM.ADMIN.PERFM.EVENT, SYSTEM.ADMIN.CHANNEL.EVENT, SYSTEM.ADMIN.CONFIG.EVENT or the SYSTEM.ADMIN.COMMAND.EVENT queues. To listen for MQFMT_EVENT and User messages on any other queue, you must modify the AAOMQLxx member of BBPARM and include the names (or name pattern) of the queues to be monitored.

Related topic

Automate-IBM-MQ-events-with-BMC-AMI-Ops-Automation-Rules

 

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