Transaction usage by control section report


Strobe produces the Transaction Usage by Control Section report if it records transaction identifiers in the sample data set. The report lists transactions in ascending order by transaction identification code, module name, and control section name. If the transaction name contains unprintable characters, Strobe prints it in hexadecimal notation.

Transaction Usage by Control Section Report

image2022-11-4_14-48-18.png

When you measure a CICS region and produce the CICS Performance Supplement, the Transaction Usage by Control Section report appears, with a different format, in the CICS Performance Supplement. For a description of the report, refer to the CICS section of the Options Guide.

Important

When you create the Performance Profile, you can supply the TUCS parameter to specify a threshold percentage of CPU time use, which can significantly shorten the length of the report that you need to review. With this parameter, the report omits transactions that use less than the amount you specify.

MODULE NAME

The name of the module or pseudo-module for which Strobe is detailing CPU use. For module names that exceed eight characters, see the note in the SECTION NAME paragraph.

SECTION NAME

The true name of the module appears in this column if the module is compressed. Otherwise, this column shows the control section name.

Important

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

COMPRESSED

The name of the control section of the module that has been compressed within a pseudo-module.

FUNCTION

A short description of the function of the control section or pseudo-section, or of the module or pseudo-module. Function descriptors appear for all pseudo-sections and pseudo-modules and, if your Strobe system programmer has supplied them, for other control sections and modules as well.

CPU TIME PERCENT

The percentage of all CPU time used on behalf of each control section of each module executed in the course of processing the transaction. 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.

CPU TIME HISTOGRAM

The histogram shows the distribution of CPU usage within each control section. Solo CPU time is indicated by the asterisk symbol (*). The remaining CPU time is indicated by the plus symbol (+). Spikes, or lengthy lines in the histogram, highlight control sections with a high proportion of activity.

MARGIN OF ERROR

The margin of error for CPU time percentages. This value also appears in the CPU MARGIN OF ERROR PCT field on the Measurement Session Data report. (See CPU MARGIN OF ERROR PCT.)

 

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