Skip to Content

Attribution reports

Attribution reports identify sites of invocation of selected service routines. Strobeproduces attribution reports for both CPU wait time and CPU execution time (see Attribution of CPU Execution Time Report). Examine these reports when system services use a high proportion of CPU resources or cause wait. These reports identify source statements that cause the activity.

Attribution of CPU Wait Time Report

image2022-11-4_15-44-37.png

Each section of the attribution report begins with a header line that identifies the invoked service routine. The header also shows the pseudo-module name, module name, control section name (when available), and a function descriptor for either the control section or the module. Reports for pseudo-module names .COBLIB, .PL/ILIB, .C370LIB, and .SVC have the format described here. For other pseudo-module names, see Program Structure and Strobe Pseudo-Entities to determine the subsystem that Strobe detected. The section of the Options-guide for the measured subsystem explains how to interpret these specialized attribution reports.

Each report detail line identifies a location in a program from which the service routine was directly or indirectly invoked. The Attribution of CPU Execution Time report shows solo and total CPU time spent in the service routine while it was invoked from that location. The Attribution of CPU Wait Time report shows the program wait time spent in the service routine while it was invoked from that location.

Attribution of CPU Execution Time Report

image2022-11-4_15-46-5.png

The location that invoked the service routine is listed under WAS INVOKED BY. The location that invoked the service routine is generally within a user-written routine and is defined by transaction, module, control section, and return address. If the invoking module or control section was a system routine, the report shows a function descriptor of either the control section or the module. If the invoking control section was a user-written routine and index data was available for the invoking control section, the report gives the line number and procedure name as well.

If the control section has not directly called the service routine, then the routine first called by the invoking location is defined under VIA by module, control section, and a brief description of its function.

XACTION

The name of the transaction that invoked the service routine, if there was one.

MODULE

The name of the module that invoked the service routine. If the invoker is a system module, the report identifies it by pseudo-module name, module name, and control section name. For module names that exceed eight characters, see the note in the SECTION paragraph.

SECTION

The name of the control section that invoked the service routine.

Warning

Note

For all module or section names that exceed eight characters, Strobegenerates 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. See Token - Longname Cross Reference report to reconcile all tokens with their long names.

FUNCTION

When measuring an application showing activity to service routines invoked by C or C++ function, the name of the C or C++ function within the section that invoked the service routine. For function names that exceed eight characters, see the note above in the description of SECTION.

RETURN

The location, in hexadecimal, where the application invoked the service routine.

LINE

The line number at which the application invoked the service routine, for an indexed Performance Profile.

PROCEDURE NAME

The name of the procedure in which the application invoked the service routine, for an indexed Performance Profile.

Warning

Note

For pseudo-sections, the RETURN, LINE, and PROCEDURE NAME columns have different meanings. The RETURN column gives the name of the control section within the pseudosection that invoked the service routine. The LINE and the PROCEDURE NAME columns together contain the function descriptor of the control section identified in the LINE column.

MODULE (under VIA)

The name of the module that invoked the service routine if it was not directly invoked.

SECTION (under VIA)

The name of the control section that invoked the service routine if it was not directly invoked. For wait only, if the invoked module controls file access activities, the report shows the data definition name of the data set currently serviced by the invoked module instead of the control section name.

FUNCTION

The function of the control section or module that invoked the service routine if it was not directly invoked.

CPU TIME PERCENT

For the Attribution of CPU Execution Time reports, the percentage of all CPU execution time used by programs executed within the address space that was spent in the invoked system routine on behalf of the invoking routine. There are two measures of CPU time:


    • SOLO shows activity without any concurrent I/O activity being performed under control of programs executing within the address space
    • TOTAL shows activity with or without any concurrent I/O activity.

WAIT TIME PERCENT

For the Attribution of CPU Wait Time reports, the percentage of wait time spent in the invoked system routine on behalf of the invoking routine. The time value is the percentage of all wait time used by programs executed in the measured job step for total wait.

 

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

BMC Compuware Strobe 18.02