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.

What IBM MQ events are

BMC AMI Ops Automation

 can listen for events, such as z/OS commands or messages, and execute Rules for the event that perform an action, such as message rerouting or creating a 

BMC AMI OpsA

 ALERT.

Messaging and queuing also generate IBM MQ instrumentation events for which BMC AMI Ops Automation for MQ can listen for and execute Rules.

BMC AMI OpsA distinguishes IBM MQ messages based on the message format:

  • MQFMT_NONE
  • MQFMT_ADMIN
  • MQFMT_CHANNEL_COMPLETED
  • MQFMT_CICS
  • MQFMT_COMMAND_1
  • MQFMT_COMMAND_2
  • MQFMT_DEAD_LETTER_HEADER
  • MQFMT_EVENT
  • MQFMT_IMS
  • MQFMT_IMS_VAR_STRING
  • MQFMT_MD_EXTENSION
  • MQFMT_PCF
  • MQFMT_REF_MSG_HEADER
  • MQFMT_STRING
  • MQFMT_TRIGGER
  • MQFMT_WORK_INFO_HEADER
  • MQFMT_XMIT_Q_HEADER
  • MQFMT_RF_HEADER
  • MQFMT_RF_HEADER_2
  • USER (used for any format except MQFMT_EVENT)

When you create a Rule, you must specify which format the message contains, or specify USER for any format except MQFMT_EVENT. A single Rule can recognize only one of these two types.

This section contains the following topics:

Related topic

Product-features-and-key-concepts-of-BMC-AMI-Ops-Automation-for-MQ

 

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