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.

Installation overview

The following table shows an overview of the 

BMC AMI Ops Automation for MQ

 installation activities.

Tip

For BMC AMI Ops Automation for MQ to automate MQS events from distributed event queues, you must verify that the connectivity between z/OS and distributed queue managers is defined, as described in Defining-connectivity.

Summary of steps

For more information, see

If you are an existing BMC AMI Ops Automation for MQ site, review the migration considerations.

The migration considerations section in the Customizing-BMC-AMI-Ops-Automation-after-installation

Enable BMC AMI Ops Automation for MQ by adding the appropriate password Keys.

Add MQ APF-authorized libraries to BMC AMI Ops Automation STEPLIB.

(optional)

Activate automatic enabling of IBM MQ events by adding MQEV=Y or a combination of MQEV=SLIPRFMCVBX to BBPARM member AAOPRMxx

(optional)

Activate the monitoring of Alias queues by adding QALIAS=Y to BBPARM member AAOPRMxx

Add BQ to the RULESET= list in AAOPRMxx.

  • Modify configuration member AAOMQLxx.
  • Include queue names against which IBM MQ Rules are written.

(optional)

Enable distributed diagnostic Rules.

Review security.

Enable IBM MQ instrumentation events on the z/OS queue manager that you want monitored.

(optional)

Enable IBM MQ instrumentation events on distributed queue manager.

If PATROL for MQ-Administrator or PATROL for MQ-Operator is installed on the z/OS system, you need to do the following steps to allow BMC AMI Ops Automation for MQ to co-exist with these products:

  • Modify member AAOMQLxx.
  • Modify existing rules to use the new event queue name.

(optional)

Define sender/receiver channel pairs between z/OS IBM MQ queue managers and distributed queue managers. This allows MQ to transmit messages and commands between the queue managers.

(optional)

Define queue SYSBMC.DISTRIB.EVENTS for distributed events and include this queue in UBBPARM(AAOMQLxx).

(optional)

Route distributed instrumentation events to SYSBMC.DISTRIB.EVENTS on a z/OS MQ queue manager to make the events available to BMC AMI Ops Automation for MQ.

(optional)

Set Up MQ command capability for distributed IBM MQ queue managers.

If MQGINHIB=ALTER or MQNSHARE=ALTER, verify that all queues to be monitored have the correct attributes.

Verify that BMC AMI Ops Automation for MQ is correctly customized (IVP).

Implement BMC AMI Ops Automation for MQ solutions.

Create site-specific IBM MQ automation Rules to capture IBM MQ messages as BMC AMI OpsA events.

Create EXECs to manipulate IBM MQ messages.

This section also contains the following topics:

 

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