IBM MQ events and Rules

The

BMC AMI Ops Automation

Rule Processor listens for IBM MQ messages and recognizes them as event type MQS.

These messages (or events) can originate from a z/OS or distributed queue manager. There are additional customization steps required for listening to MQS events from distributed queue managers.

BMC AMI OpsA distinguishes between different IBM MQ messages by their format in the message descriptor. The following table lists these message formats and descriptions.

Message format	Description
MQFMT_NONE	No format
MQFMT_ADMIN	Command server request/reply message
MQFMT_CHANNEL_COMPLETED	Channel has ended
MQFMT_CICS	IBM CICS Information Message
MQFMT_COMMAND_1	Type 1 command reply message
MQFMT_COMMAND_2	Type 2 command reply message
MQFMT_DEAD_LETTER_HEADER	Dead Letter Message
MQFMT_EVENT	Event Message
MQFMT_IMS	IMS Information Message
MQFMT_IMS_VAR_STRING	IMS Variable String Message
MQFMT_MD_EXTENSION	Message Descriptor Extension
MQFMT_PCF	Programmable Command Format
MQFMT_REF_MSG_HEADER	Reference Message Header
MQFMT_STRING	Character String
MQFMT_TRIGGER	Trigger Message
MQFMT_WORK_INFO_HEADER	Work Information Message
MQFMT_XMIT_Q_HEADER	Transmission Queue Message
MQFMT_RF_HEADER	Rules and formatting header
MQFMT_RF_HEADER_2	Rules and formatting header version 2

The origin of the message may be from a z/OS queue manager or a distributed queue manager. When you create a Rule, you must specify the format of the message. A single Rule can recognize only one specified format. However, by specifying USER, the Rule can fire for any format except MQFMT_EVENT.

This section contains the following topics:

IBM MQ events and Rules

BMC AMI Ops Automation 8.4

On this page