Verifying the installation

The installation verification procedure is a compiled REXX EXEC named QMQIVP00 that tests the configuration of the BMC AMI Ops Automation environment and verifies the current status of IBM MQ instrumentation event categories and theBMC AMI OpsA ability to automate events.

Before using the installation verification procedure, you must complete Defining-connectivity. After defining the needed queues and channels, you must start the IBM MQ command server and the IBM MQ listener tasks. On z/OS, the command server normally starts automatically after the queue manager starts.

Related topic

Installation-overview

After the command servers and listeners are active, the sender channels on both sides of the connection can be started. For more information on starting command servers, listeners, and channels, see the IBM publication IBM MQ Script (MQSC) Command Reference.

Use the QMQIVP00 EXEC to verify that you have defined and connected to z/OS and distributed queue managers successfully. This EXEC can be scheduled from the BBI Log or from within an EXEC.

See Diagnosing-BMC-AMI-Ops-Automation-for-MQ-errors for a description of how to diagnose installation errors.

The syntax for invoking the QMQIVP00 EXEC from the BBI Log is

 COMMAND ===> %QMQIVP00 function LM RM CQ

where

Parameter

Description

Function

Required user-specified value

Possible values are:

  • IE creates a z/OS instrumentation event condition. Use this to test the BMC AMI OpsA connection to the z/OS queue manager and the BMC AMI OpsA ability to automate events on that queue manager
  • CMD displays the status of z/OS instrumentation event conditions for the specified queue manager
  • NCMD displays the status of z/OS instrumentation event conditions for the specified queue manager
  • NIE creates a distributed instrumentation event condition. Use this to test BMC AMI OpsA connection to the distributed queue manager and the BMC AMI OpsA ability to automate events on that queue manager.

Local_qmgr_id


Required value where you type the local queue manager ID

You must type a local queue manager name to use the EXEC even if you are trying to query the status of distributed queue managers.

Remote_qmgr_id

Local queue manager’s alias name of a distributed queue manager. This field is required when you are querying a distributed (or remote) queue manager. The local queue manager alias name of a distributed queue manager is created in Setting-up-BMC-AMI-Ops-Automation-for-MQ-to-issue-commands-to-distributed-queue-managers.

This is the name that must be used when you are querying a distributed (or remote) queue manager with this EXEC.

Remote_qmgr_command_queue

Optional value where you type the name for a distributed command queue

The default value is SYSTEM.ADMIN.COMMAND.QUEUE.

This parameter is not applicable to z/OS queue managers.

Examples of verifying the installation

Following are some examples about how to use the QMQIVP00 EXEC to verify that you have successfully completed implementing communications between BMC AMI Ops Automation for MQ and z/OS queue managers and distributed queue managers.

Example

Displaying the status in the BBI Log of z/OS instrumentation event conditions for a local queue manager named csbe:

Command ===> %QMQIVP00 CMD JBQ

The results are displayed in the BBI Log.

.QMQIVP00 - DISPLAY STATUS OF CURRENT INSTRUMENTATION EVENT CATEGORIES
.QMQIVP00 - CSQM409I @JBQ
.QMQIVP00 - QMNAME(JBQ)
.QMQIVP00 - INHIBTEV(ENABLED)
.QMQIVP00 - LOCALEV(ENABLED)
.QMQIVP00 - REMOTEEV(ENABLED)
.QMQIVP00 - STRSTPEV(ENABLED)
.QMQIVP00 - PERFMEV(ENABLED)
.QMQIVP00 - CONFIGEV(ENABLED)
.QMQIVP00 - CMDEV(ENABLED)
.QMQIVP00 - CHLEV(ENABLED)
.QMQIVP00 - SSLEV(ENABLED)
.QMQIVP00 - BRIDGEEV(ENABLED)

This output shows the name of the local queue manager and the status of the instrumentation events in that queue manager. Use this output to determine which instrumentation events are enabled.

Example

Creating a z/OS instrumentation event condition for a local queue manager named csbe:

Command ===> %QMQIVP00 ie CSBE

The results are displayed in the BBI Log.

.QMQIVP00 - z/OS INSTRUMENTATION CONDITION                           
.QMQIVP00 - SUCCESSFULLY CREATED

This output shows that both BMC AMI OpsA and the z/OS queue manager are properly configured to allow BMC AMI OpsA to automate instrumentation events on the specified z/OS queue manager.

Example

Displaying the status of distributed (remote) instrumentation event conditions for a remote queue manager whose local queue manager alias is epesin:

Command ===> %QMQIVP00 ncmd CSBE EPESIN

The results are displayed in the BBI Log.

.QMQIVP00 - DISPLAY STATUS OF CURRENT INSTRUMENTATION EVENT CATEGORY
.QMQIVP00 - AMQ8408: Display Queue Manager details.
.QMQIVP00 - QMNAME(EPESIN)
.QMQIVP00 - AUTHOREV(DISABLED)
.QMQIVP00 - INHIBTEV(DISABLED)
.QMQIVP00 - LOCALEV(DISABLED)
.QMQIVP00 - REMOTEEV(DISABLED)
.QMQIVP00 - CONFIGEV(ENABLED)
.QMQIVP00 - STRSTPEV(ENABLED)
.QMQIVP00 - CHLEV(DISABLED)
.QMQIVP00 - SSLEV(DISABLED)

This output shows the name of the distributed queue manager and the status of the instrumentation events on that remote queue manager. Use this output to determine which instrumentation events are enabled.

Example

Creating a distributed instrumentation event condition for a remote queue manager whose local queue manager alias is epesin:

Command ===> %QMQIVP00 nie CSBE EPESIN

The results are displayed in the BBI Log.

.QMQIVP00 - NON z/OS INSTRUMENTATION EVENT CONDITION        
.QMQIVP00 - SUCCESSFULLY CREATED

This output shows that all of BMC AMI OpsA, the z/OS queue manager, and the remote queue manager are properly configured to allow BMC AMI OpsA to automate instrumentation events on that remote queue manager.

 

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