Installation overview

The following table shows an overview of the MainView AutoOPERATOR for MQ installation activities.

Tip

For MainView AutoOPERATOR 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.

Table 1. Installation activities—summary

Summary of steps

For more information, see

If you are an existing MainView AutoOPERATOR for MQ site, review the migration considerations.

The migration considerations chapters in the MainView AutoOPERATOR Customization Guide

Enable MainView AutoOPERATOR for MQ by adding the appropriate password Keys.

Specifying product option password keys

Add MQ APF-authorized libraries to MainView AutoOPERATOR STEPLIB.

Adding IBM MQ APF–authorized libraries to the STEPLIB DD card

(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

Modifying AAOPRMxx parameter settings

Add BQ to the RULESET= list in AAOPRMxx.

Modifying AAOPRMxx parameter settings

  • Modify configuration member AAOMQLxx.

  • Include queue names against which IBM MQ Rules are written.

(optional)

Enable distributed diagnostic Rules.

Enabling 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 MainView AutoOPERATOR for MQ to co-exist with these products:

  • Modify member AAOMQLxx.

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

Setting up MainView AutoOPERATOR for MQ to co-exist with BMC Performance Manager for IBM MQ for z/OS and OS/390

(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.

Defining connectivity

(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 MainView AutoOPERATOR for MQ.

Defining connectivity

(optional)

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

Defining connectivity

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

Customizing MainView AutoOPERATOR for MQ

Verify that MainView AutoOPERATOR for MQ is correctly customized (IVP).

Verifying the installation

Implement MainView AutoOPERATOR for MQ solutions.

MainView AutoOPERATOR for MQ solutions

If SAAREXX/370 is not installed, install REXX/370 alternate library.

MainView AutoOPERATOR for MQ solutions

Create site-specific IBM MQ automation Rules to capture IBM MQ messages as MainView AutoOPERATOR events.

Create EXECs to manipulate IBM MQ messages.

(optional)

Create EXECs to manage and maintain distributed IBM MQ queue managers.

Using the Command MQ Automation Power Line (APL) EXEC

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments