Help
Transaction CPU Usage
The Transaction CPU Usage report shows the distribution of CPU usage among transactions processed by the target subsystem. The report appears when Strobe records transaction identifiers in the sample data set.
Activity within IBM-supplied modules, such as I/O service routines, compiler library routines, and SVCs, is attributed to pseudo-sections whose names begin with ".". The true name of the module appears when you expand an entry to the Section level.
The presentation uses a tree map method for displaying data.
Report details
Select a resolution from the Resolution drop-down list box to adjust the view of the Transaction CPU Usage report. Changing the value of the code block in bytes will adjust the resolution of the report. A large code block size allows for a more generalized view of CPU activity. A small code block size allows for a more specific view of CPU activity. The code block default is 2 bytes. An adjusted code block will remain as such until the session ends or another value is selected.
This feature is only available for profiles created by Reporter version 5.2 and greater.
Pseudo-Module or Pseudo-Section is the name
Transaction is the name of the active transaction. If the transaction name contains unprintable characters, the report shows it in hexadecimal notation.
Description briefly explains the function of the transaction. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.
Transaction Count is the total number of times that the transaction executed during the measurement session.
Avg Service Time (sec) shows the average wall clock time for the transaction's duration.
CPU % Execution shows the percentage of CPU activity with or without any concurrent I/O activity for the transaction.
Click 
next to a Transaction to view additional detail:
Pseudo-Csect is the name of the active pseudo-entity.
Description is a short description of the function of the pseudo-entity.
CPU% Execution shows the percentage of CPU activity with or without any concurrent I/O activity for the module.
Click next to the Pseudo-Csect to view additional detail:
Module is the name of the active module.
Description briefly explains the function of the module. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.
CPU% Execution shows the percentage of CPU activity with or without any concurrent I/O activity for the section or csect.
Note: For all module or section names that exceed eight characters, Strobe generates a token, which is an eight-byte identifier. The token comprises the first four characters of the module or section name followed by a hyphen (-) and then the last three characters of the name. Refer to the Token Long Name Cross Reference report to reconcile all tokens with their long names.
Click next to the Module to view additional detail:
Section is the name of the active control section.
Description briefly explains the function of the section. Function descriptions appear for all Strobe pseudo-entities and for transactions with descriptions supplied by the system programmer.
CPU% Execution shows the percentage of CPU activity with or without any concurrent I/O activity for the section or csect.
Analysis tips
Click an underlined name of a Transaction, Pseudo-Csect, Module, or Section to see an expanded description.
If high CPU execution within a transaction or ADABAS region was caused by library routines, SVC activity, or system routines (DB2, CICS, and so on), refer to the Attribution of CPU Usage report to determine what invoked this activity.
If a specific module is responsible for high CPU use within a transaction, refer to the Program CPU Usage report to identify the procedures or offsets within that module that are using the CPU.
Related Topics