Setting up the IBM Z APM Connect IBM MQ monitoring agent subsystem

Edit online

IBM MQ monitoring agent subsystem is required for the collection of the application performance metrics for message flows through IBM MQ. To track message flows through IBM MQ, define a subsystem for the IBM Z® APM Connect IBM MQ Monitoring agent.

About this task

Note: Z APM Connect MQ Monitoring agent subsystem is not required for Z APM Connect IMS Data Producer to track IMS transactions.

The IBM Z APM Connect IBM MQ Monitoring subsystem is used only as a means of scheduling the initialization routine in the main scheduler address space. The MVS subsystem interface for it is not activated or used.

Typically, you would set up only one subsystem for all the Z APM Connect Base address spaces that are running on the same logical partition (LPAR).

To define a IBM Z APM Connect IBM MQ Monitoring subsystem, the following modules that are delivered in the &shilev.SAGMMOD library must be placed in a LNKLST data set. If LNKAUTH=LNKLST is not used, the data set must be also explicitly APF-authorized.

AGMQSSIN
Subsystem initialization routine
AGMQSTBX
MQI intercepting stub routine

To ensure that your changes remain in effect after a system initial program load (IPL), complete the steps in Updating SYS1.PARMLIB members.

Optionally, to set up the IBM Z APM Connect IBM MQ subsystem without an IPL, you can follow the instructions in Setting up the subsystem without an IPL. For example, it is the first time that you are setting up an IBM Z APM Connect IBM MQ Monitoring agent subsystem.

By default, AGMQ is the IBM Z APM Connect IBM MQ subsystem that is used by the agent. If a IBM Z APM Connect IBM MQ subsystem is defined with a name other than AGMQ, you must update the runtime member of the Z APM Connect Base address space to explicitly specify the subsystem name as described in Using a subsystem other than AGMQ.

Note: Up to 32 IBM MQ regions can be supported by one IBM MQ Monitoring Agent Subsystem. If you plan on monitoring more than 32 IBM MQ regions, you need an extra IBM MQ Monitoring Agent Subsystem by using a unique subsystem ID. For more information, see Using a subsystem other than AGMQ.
Note: If IBM MQ is stopped or restarted for any reason, you need to either recycle the Base address space or recycle the MQ subsystem by issuing the AGMQ INIT dispatcher command.
  • Before recycling the Z APM Connect Base, issue the AGMQ TERM command for all MQ subsystems connected to the Base.
  • Before recycling the MQ subsystem, issue the AGMQ TERM command for each MQ subsystem to be recycled.

AGMQ TERM command needs to be issued to clear obsolete entry in subsystem communication table's extension. Otherwise the table will fill up over time and cause Z APM Connect to issue an AGMQ0034E error. See command details in the reference section: Base operation.