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.

How BMC AMI Ops Automation connects to IBM MQ

For 

BMC AMI Ops Automation for MQ

 to perform automation of IBM MQ events, 

BMC AMI Ops Automation

  must make connections to IBM MQ local queue managers. 

BMC AMI Ops Automation for MQ

 determines which queue managers to connect with automatically and dynamically based on automation needs.

BMC AMI Ops Automation for MQ can connect directly only to IBM MQ queue managers running on the same z/OS image. However, IBM MQ instrumentation events on distributed operating systems can still be automated by BMC AMI Ops Automation for MQ if the distributed system is connected to a z/OS queue manager. Refer to Defining-connectivity for more information.

Connections between z/OS queue managers and BMC AMI OpsA can be made in one of two ways:

  1. For Rules created for event type MQS, BMC AMI OpsA searches for the queue manager during Rule enablement. If the queue manager is found and a connection has not already been established, a connection is made.

  2. When a queue manager completes initializing and issues either the message CSQ9022I XXXX CSQYASCP 'STA QMGR' NORMAL COMPLETION or CSQ9022I XXXX CSQYASCP 'START QMGR' NORMAL COMPLETION, BMC AMI Ops Automation for MQ detects the message.  MBMC AMI Ops Automation for MQ checks all enabled MQS-initiated Rules to determine if the Selection Criteria Queue Manager value matches the queue manager ID that is starting up and attempts to connect to that queue manager.  If the CSQ9022I message is not issued because it has been added to the EXCLMSG attribute of the MQ ZPARM module, BMC AMI Ops Automation for MQ will not recognize the initialization of IBM MQ.

    Therefore you must ensure that the CSQ9022I message is not suppressed or BMC AMI Ops Automation for MQ might not be able to connect to IBM MQ.  If BMC AMI Ops Automation for MQ Rules cannot detect the CSQ9022I message, the only way to connect to the queue manager is to have an MQS Rule or a Ruleset that contains an MQS Rule to be enabled.  When the MQS Rule is enabled, BMC AMI Ops Automation for MQ  attempts to connect to the queue manager.

At the time of connection, only the eligible queue names listed in BBPARM member AAOMQLxx become eligible for automation. If new queues are added later that require automation, you must refresh the list of eligible queues. For more information about including specific queue managers in BBPARM member AAOMQLxx, refer to Parameters-for-BBPARM-member-AAOMQLxx.

Note

At BMC AMI OpsA startup time or during a reset situation, BMC AMI Ops Automation for MQ creates the following IBM MQ queues for internal processing of commands and replies the following where xxxx is the BMC AMI OpsA subsystem ID and yyyy is the name of the queue manager:

  • BBMVAO.COMMAND.REPLY.MODEL
  • BBOMVAO.xxxx.RULES.INITIALIZE
  • BBOMVAO.xxxx.RULES.CMDREPLY
  • BBOMVAO.EXEC.REPLY.xxxx.yyyy

If you do not specify a queue manager name, IBM MQ copies and uses the STGCLASS value from queue SYSTEM.DEFAULT.MODEL.QUEUE on a new model queue definition. If your MQ does not have a storage class that matches what is in SYSTEM.DEFAULT.MODEL.QUEUE and copied into BBOMVAO.COMMAND.REPLY.MODEL, then BMC AMI Ops Automation for MQ will fail to properly initialize and MQ messages and events will not be automated.  You will see messages similar to these in the MQ joblog:                                   

                    

CSQN207I @JBQ COMMAND SERVER UNABLE TO OPEN REPLY TO QUEUE            

CSQN203I @JBQ QUEUE BBOMVAO.JB81.RULES.INITIALIZE,  578              

MQCC=2 MQRC=2085 (MQRC_UNKNOWN_OBJECT_NAME)                          

                                                                      

You can deal with this situation one of three ways:                  

  • If you have not already started BMC AMI OpsA and experienced this problem (such as there is no XXXXXX storage class) you can manually create the BBOMVAO.COMMAND.REPLY.MODEL model queue using the attributes specified below.  Specify a valid storage class value for your site.   

      • SHARE            

      • INDXTYPE(CORRELID)

      • DEFSOPT(SHARED)  

      • DEFTYPE(PERMDYN) 

  • If this problem has already occurred and now model queue BBOMVAO.COMMAND.REPLY.MODEL exists with an invalid storage class, you can simply alter the queue definition and change the STGCLASS attribute to one that is acceptable on your system.  When BMC AMI Ops Automation for MQ starts, it will continue on and only change other attributes if they are incorrect.                                                            
  • You can change SYSTEM.DEFAULT.MODEL.QUEUE STGCLASS attribute to one that is valid for your site.                                     

After making this change, if BMC AMI OpsA is still running, you can enter the BBI command .E MQ and BMC AMI Ops Automation for MQ will restart initialization.  Otherwise start BMC AMI OpsA and the problem should be resolved.

Other than a possible issue with the model queue BBOMVAO.COMMAND.REPLY.MODEL described above, you should not be concerned with these queues or events related to these queues unless error messages are issued regarding them.

Related topic

Overview-of-BMC-AMI-Ops-Automation-for-MQ

 

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