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.

Generating instrumentation events


Instrumentation events, recognized by 

BMC AMI Ops Automation

 by their format, MQFMT_EVENT, are generated by queue managers.

It might be possible to configure a queue manager to not generate instrumentation events. In this case, BMC AMI OpsA will not be able to hear them and, therefore, Rules for these events will not fire.

Use the AAOPRMxx parameter MQEV=Y|N (or some combination of MQEV=SLIPRFMCVBX) to specify whether BMC AMI Ops Automation for MQ will automatically alter queue managers to generate instrumentation events. If the queue manager has not been configured to generate instrumentation events and you choose the default setting of MQEV=N; BMC AMI OpsA will not hear the events, and MQS event Rules will not fire.

For BMC AMI OpsA to hear the events, you must specify MQEV=Y (or any combination of MQEV=SLIPRFMCVBX values). When MQEV=Y is specified, BMC AMI OpsA alters queue managers (SLIPRF types only) automatically when it is started, to generate instrumentation events if they were originally disabled.

When the MQEV parameter is left with the default setting of NO (MQEV=N), BMC AMI OpsA will not automatically alter queue managers to generate instrumentation events. Warning messages are issued during BMC AMI OpsA connection to a queue manager to inform you about any classes of events that are not enabled.

 

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