12.3.14 F14 - DB2 CPU by Plan/Stored Procedure F14 shows how CPU resource was consumed by each stored procedure measured during the sampling interval. The percentage of time is reported for each DB2 plan under which measured stored procedure activity was recorded. Expand a plan line to see a further breakdown of time consumption by category, as shown in Figure 12-83. Figure 12-83 F14: DB2 CPU by Plan/Stored Procedure 12.4 MQ measurement Because the TRADER application has no MQSeries command, to illustrate MQ reports we use a specific CICS/MQSeries transaction. We do not spend much effort on the things that are common to Application Performance Analyzer and that have been described in the previous chapter, but rather focus on the unique aspects of using Application Performance Analyzer with the batch job accessing MQSeries resources. 12.4.1 Observation session request definition We need to monitor the CICS region named CICSC23G with the following characteristics: A sampling rate of 1,000 samples per second. A duration of 1 minute. The measurement file has to be retained for 30 days. Only MP* transactions have to be recorded. CHABERT has to be notified at the end of the measurement. By entering the NEW command line on the Observation List (R02) panel, Application Performance Analyzer will display the Schedule New Measurement (R03) panel. CICS and MQseries data extractor has to be turned on to get both CICS and MQSeries data. Chapter 12. Application Performance Analyzer: analyzing a job with subsystem 307