How can I find out why MainView for MQ is unable to monitor a particular queue?

Use the following procedure:

  1. Review the BBI-SS PAS’ Start messages in the BBI Journal (or in the joblog) and look for the QA1113E message: 

    QA1113E UNABLE TO INITIALIZE AO for MQ TASK

    The QA1113E error message occurs when you bring up a queue manager after the BBI-SS PAS is started and the system is unable to initialize the MainView AutoOPERATOR for MQ task. If you receive this error, you may need to contact BMC Customer Support for assistance.

    If this message is not in the BBI Journal or the joblog, the BBI-SS PAS was started correctly.

  2. Review the joblog messages for any error messages involving the queue manager and its channel initiator.

  3. Verify that the IBM MQ APF-authorized libraries are added to the STEPLIB DD CARD properly.If they are not added correctly or are missing, you may receive error message QA1114E. The error message and reason are displayed here:

    QA1114E  WebSphere MQ STEPLIB MISSING/INVALID                              
    REASON   AO for MQ tried to initialize, but failed because the
    STEPLIB did not specify a valid IBM MQ load library.
    SYSTEM   AO for MQ will not initialize.                                
    ACTION                                                                 
    USER     Check the JCL for the BBI/SS to make sure the STEPLIB DD      
    ACTION   statement contains the IBM MQ Authlib.

    If the IBM MQ libraries are missing from the STEPLIB DD concatenation, add them. The IBM MQ libraries must be at or above the level of the z/OS queue managers that are going to be automated. Also review the Specifying-product-option-password-keys.

  4. Verify that the QAO product option key is properly installed and active.For information about how the QAO key is installed, refer to the sectionSpecifying-product-option-password-keys.

    If you have already followed the instructions, perform the following steps to ensure that the product was installed properly:

    1. In the BBI Journal, issue the BBI command .D A (display active).This command shows all currently active products in the BBI-SS PAS.

      Example

       

      AA0101I  AAO VERSION 6.2.0 STARTED ON 17-JAN-2001 AT 09:53:11   
      AA0102I      CAO - ACTIVE                                     
      AA0103I      IAO - ACTIVE                                     
      AA0104I      MAO - ACTIVE                                     
      AA0106I      QAO - ACTIVE

      If QAO is not listed as active, MainView AutoOPERATOR for MQ either has not been installed or has been installed incorrectly. For information about installing the product, refer to Implementing-MainView-AutoOPERATOR-for-MQ.

    2. In the BBI Journal issue the BBI command .D KEYS (display keys).This command shows all currently valid product option keys.

      Example

       

      CF8701I  COPY PROTECTION KEY STATUS:                   
      CF8702I  PRD     CPUID      EXP        SYS         STATUS   
      CF8703I  -------   -------------   ---------     ---------  
      CF8704I  MAO?9672-15-*1317-99365-C4B0        VALID     
      CF8704I  MAO?9672-08-*3481-99365-4CA4        CPU-ERR   
      CF8704I  QAO-9672-15-11317-99365-D0A5        VALID     
      CF8704I  QAO-9672-08-13481-99365-D2DF        CPU-ERR

      If you have typed an invalid key, as described in Specifying-product-option-password-keys, or you do not have the key, contact BMC Software Customer Support to obtain the key.

  5. Verify that a Rule exists that refers to the queue and the queue manager and that the Rule and its Rule Set are enabled.

  6. Verify the connection to the queue manager by using the MainView AutoOPERATOR for MQ Workstation panel and issue the BBI command .RESET MQ xx, where xx represents the two-character suffix of the AAOMQLxx member, to reset the queue manager.If the queue manager is not connected, follow the instructions in Implementing-MainView-AutoOPERATOR-for-MQ to connect it.

    For information about how to use the Workstation display, refer to MainView-AutoOPERATOR-for-MQ-automation-statistics.

  7. In the BBI Journal, issue the %QMQDSP00 command for a list of all queues and their status to determine which queues are eligible for automation, and find the specific queue in the list to verify that it will be monitored.An example of the output from the %QMQDSP00 EXEC follows:

    .QMQDSP00 EID=00064 excl_by_user 32 local CSAE EPESIN.XMITQ          
    .QMQDSP00 EID=00064 excl_by_user 32 remote CSAE CICSPRD1                
    .QMQDSP00 EID=00064 excl_by_user 32 alias CSAE CICSPRD1.ALIASQ0         
    .QMQDSP00 EID=00064 included 27 local CSAE CICSPRD1.QUEUE1              
    .QMQDSP00 EID=00064 included 27 local CSAE CICSPRD1.QUEUE10             
    .QMQDSP00 EID=00064 included 27 local CSAE CICSPRD1.QUEUE11

    The queues named CICSPRD1.QUEUE* are eligible for automation.

    If the queue is currently excluded, edit BBPARM member AAOMQLxx to add it to be included and issue a .RESET MQ xx command. Refer to Parameters-for-BBPARM-member-AAOMQLxx for more information.

  8. Use MainView for MQ or z/OS commands to verify that the z/OS queue manager is usable.Refer to the IBM manual IBM MQ Problem Determination Guide or the IBM Knowledge Center for more information about any problems you may encounter.

    Use MainView for MQ or PATROL for MQ-Administrator to verify that the event queues are remote and working and the channels, transmission queue, and queue manager alias are working.

 

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