In order to use the MQSeries® Performance Analysis Reports,
the MQSeries data extractor must be turned on when
the Observation Request is entered. You must select the MQS data extractor
in the Enter an Observation Request panel.
This data extractor provides the ability to observe/sample and
report on MQSeries interface calls (both dynamic and static)
in Batch, IMS™ and CICS® programs. More specifically,
to show the CPU and wait time spent in MQSeries interface
calls and to attribute the time spent to a particular MQSeries interface
call.
When the MQSeries data extractor is selected, Application Performance Analyzer will
record the following information in the sample file for each MQSeries call
that it observes:
- Environment (Batch, IMS or CICS)
- Load module that issued the call
- Offset within the load module of the return address from the MQ
call
- Type of MQI call (MQOPEN, MQGET, etc.)
- Queue Manager name
- Object name (for example, the queue name)
- Message size (actual length for MQPUT/MQPUT1, buffer length for
MQGET)
- MQ Options (for MQOPEN, MQGET, MQPUT MQCLOSE)
- Message type, priority and persistence
- Transaction ID (CICS and IMS)
Note:
In an IMS environment, Application Performance Analyzer might
not be able to determine the default Queue Manager name for some samples
if the Application Performance Analyzer task has not previously sampled any. This might
result in the MQ object name being unknown for the first few calls.
Subsequent sampling runs will obtain the MQ object name for each sample.
[ Top of Page | Previous Page | Next Page | Contents | Index ]