Skip to Content
Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Monitor for MQ 5.6.

BMC Extensions for IBM MQ on z/OS

On z/OS, the implementation of BMC Extensions for IBM MQ is called MQE.

MQE provides the following types of statistics:

  • Qstats or Queue Performance data provides information about the queue such as API counts and PUT and GET minimum, maximum, and average values.
  • Detailed statistics are raw statistical data that is collected on z/OS by using a record key of the named object, application name, and application type. MainView for MQ provides several different views of this data.
  • Trace capabilities trace API calls according to options that are specified in EXITOPT. You can view these traces in MainView for MQ.

Install MQE by adding a step to execute the program MMAHINIT before the execution of CSQYASCP in the queue manager master JCL procedure. MMAHINIT calls routines that perform the following functions:

  • build control blocks
  • read the EXITOPT file and then process the command or save it for later
  • set up for initialization in the QMGR step
  • call product preinitialization

MMAHINIT is called with the product ID parameter. The product ID for statistics and trace is MQT. When you use this parameter, statistics and trace functions are installed.

When MQE is initialized, it creates two data spaces for the qmgrMSTR address space to gather MQ call data. These data spaces are named as qmgrMQTR and qmgrBMCX. When the PAS is initialized one data space, named MQEXqmgr, is created to process the MQ call data collected by MQE.    


 

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

MainView for MQ 5.5