Reports produced by Strobe options

Your Performance Profile includes additional reports and option-specific data if your installation includes any of the following Strobe options and measured language environments:

• Adabas/Natural
• C and C++
• CA Gen
• CA-IDMS
• CICS
• Db2
• Db2 DDF
• IMS
• WebSphere MQ
• z/OS UNIX System Services.

The corresponding section of the Options-guide details how to interpret these Performance Profile reports.

With the AutoStrobe history function, you can print or export the measurement session history reports that are created and displayed by Strobe/ISPF. Examples of these reports are shown and described in the User-Guide.

Subsystem attribution reports

For each Strobe subsystem option, Strobe produces attribution reports specific to the subsystem it supports. For a complete description of the reports, refer to the related section of the Options-guide.

Strobe reports on C/C++ applications

Strobe produces two reports that show information specific to the performance of C and C++ applications. Strobe also reports on attribution to C/ C++ functions; see Attribution Reports.

C/C++ Section Usage Summary

The C/C++ Section Usage Summary report provides an overview of the CPU usage in the CSECTs within each module that Strobe measured. This section describes each of the fields on this report.

MODULE NAME

The name of the module which is responsible for CPU usage.

SECTION NAME

The name of the sections within the module identified in the MODULE NAME field for which Strobe is detailing CPU usage. For function names that exceed eight characters, see the note above in the description of MODULE NAME.

% CPU TIME

The total percent of CPU time used in class code plus system services activity attributed to class code.

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

CPU TIME HISTOGRAM

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

C/C++ Section Usage Summary Report

The CPU Usage by C/C++ Function report shows execution and attribution activity for a C or C++ module, class, or function. In the header lines, the report reflects the lowest level at which Strobe detected activity. In the detail lines the report indicates the offset within the lowest level—the module, class, or function—at which Strobe detected activity. This example shows a Performance Profile for which indexing was requested.

CPU Usage by C/C++ Function Report

In the header lines this report lists:

MODULE

The name of the module for which Strobe is detailing CPU usage.

SECTION

The name of the section within the module identified in MODULE for which Strobe is detailing CPU usage.

FUNCTION

The name of the C or C++ function within the section identified in SECTION for which Strobe is detailing CPU usage. For all method 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. See Token - Longname Cross Reference report to reconcile all tokens with their long names.

STMT NUMBER

The line number of the C or C++ program that corresponds to the offset within the module, section, or function at which Strobe detected activity. This field is blank if the Performance Profile was not indexed.

STATEMENT

The text of the statement found in the statement number reported in STMT NUMBER. This field is blank if the Performance Profile was not indexed.

OFFSET

The location by offset within the module, section, or function at which Strobe detected activity. The lowest level in the header line indicates whether this is an offset within a module, section, or function.

% CPU TIME

The percent of CPU time used by the module, section, or function that exceeds the value specified with the CRPT parameter (default .01%).

• 
  
  • SOLO shows activity without any concurrent I/O or CPU 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 distribution of CPU usage within each class. Solo CPU time is indicated with the asterisk symbol (*). The remaining CPU time is indicated with the plus symbol (+). Spikes, or lengthy lines in the histogram, highlight classes with a high proportion of activity.

Strobe for CICS reports

Strobe produces two types of CICS-related reports: the CICS Performance Supplement and the CICS Transaction Profile.

CICS performance supplement

The CICS Performance Supplement provides CICS-specific reports showing time distribution of transaction activity, transaction activity, network activity, I/O activity, configuration parameters, and system-wide statistics.

Time distribution of transaction activity level report

The Time Distribution of Transaction Activity Level report shows, for the duration of the measurement session, the interactive transaction load placed on the CICS region and the level of performance of CICS under the transaction load. This report comprises four subreports:

• Time Distribution of Transaction Arrivals shows how the arrival rate of interactive transactions varied during the session.
• Time Distribution of Transaction Service Time shows the amount of time, in seconds per input message, that CICS spent processing the transactions whose arrival distribution is shown in the Time Distribution of Transaction Arrivals subreport.
• Time Distribution of Data Base Operations shows the time variation of input and output operations performed by CICS on the database while processing the transactions.
• Time Distribution of Transaction Inputs, Processing, and Outputs shows, for each 1% of the measurement session, the major statistics of input operations, processing, and output operations.

Transaction activity report

The Transaction Activity report shows the details of processing for individual transactions and transaction processing programs. It contains the following subreports:

• Transaction Summary shows, for every transaction that was invoked during the measurement session, its type and class, invocation count, CPU time, service time statistics, and initial processing program.
• Transaction Exceptions shows, when an exceptional condition has occurred for a transaction during the measurement session, the values of exception counters for the transactions.
• Processing Program Statistics shows the CICS activity of programs named in the CICS Program Processing Table.
• IX_pseudo_transactions •CPU Usage by Control Section for Transaction name shows, for each transaction and each CICS pseudo-transaction, the CPU time spent in the control sections of the modules executed for the transaction.

Network activity report

The Network Activity report shows the data communication operations that CICS performed during the measurement session to collect transactions and input messages from terminals and to deliver output messages to terminals. It has two subreports:

• Terminal Statistics shows the terminal status and data communication activity for each terminal that was active during the measurement session.
• Terminal Exceptions shows the status and error counts for each terminal associated with an exceptional condition during the measurement session.

Input-output activity report

The Input-Output Activity report shows the input and output activity for all CICS files that were active during the measurement session. It is comprised of three subreports:

• Summary of Input-Output Operations summarizes all input and output operations, except for communication activity, during the session.
• Data Base Operations shows for each type of data base (VSAM, BDAM, ISAM, and DL/I) the number and type of input and output operations for each file accessed during the session.
• Number of Output Operations to Transient Data Queues shows the number and type of output operations for every transient data queue to which CICS wrote a record during the measurement session.

Configuration parameters and system-wide statistics report

The Configuration Parameters and System-Wide Statistics report shows several counts that apply to the entire CICS region and the values of several CICS parameters that affect the performance of the region. It has seven subreports:

• Task Statistics shows the number and types of tasks that CICS created to service the region.
• Classed Tasks Statistics shows the number and types of classed tasks that CICS created.
• Storage Statistics shows storage control statistics for main storage acquisitions and releases, failed conditional storage requests, storage violations, and the incidence of other storage-related occurrences.
• VTAM Statistics shows performance statistics for VTAM operations performed for the CICS region.
• Temporary Storage Statistics shows performance statistics for operations on CICS temporary storage.
• Transient Data Statistics—Buffer and String Statistics shows statistics related to buffers, strings, control intervals, and input/output operations on transient data queues.
• Miscellaneous Statistics shows statistics related to storage dumps and dynamic transaction backout operations.

CICS Transaction Profile

The CICS Transaction Profile provides CICS-specific reports that detail CICS transaction and region level information.

Transaction summary

The Transaction Summary report is the first of the CICS transaction and region level reports. It provides high-level information for all user, mirror, system, or Strobe generated pseudo-transactions. For user and mirror transactions, it attributes mean service time to the following categories: dispatch delay (the transaction is ready to execute but waiting to be dispatched), suspend (the transaction is waiting for an external resource), and execution (the transaction is running). For user and mirror transactions it also indicates whether detailed transaction information has been provided. It provides execution counts for user transactions, mirror transactions, and most system transactions. It shows CPU consumption for all transactions.

Transaction profile report

The Transaction Profile report helps you to target, identify, and understand performance problems at the transaction level. It consists of three subreports:

• CICS API Service Time shows, for a transaction, the subsystem API commands within a module and control section. The report shows the command, the resource that the command is targeting, the DBRM statement number (where applicable), the offset from which the command was issued, and the mean service time, which is attributed to suspended and executing states. If you have Strobe for Db2, Strobe for IMS, or Strobe for WebSphere MQ installed, Strobe will attribute the activity back to the command in the program that issued the subsystem call.
• CICS Non API Service Time accounts for service time that is not directly related to API commands. For resource type and resource name, this report shows the dispatch delay and suspend time. For modules and control sections, it shows execution time.
• CICS API Service Time Detail provides further detail for the information provided in the CICS API Service Time report, breaking down suspend and execution time into more discrete components.

CICS region level reports

The CICS region level reports provide an overall picture of suspend and dispatch delay time across an entire CICS address space. There are two region level reports:

• Region Suspend by Class provides the percentage of region suspend time and the average transaction suspend time for the various categories of suspend reasons.
• Region Suspend by Resource Within Class provides for each of the categories of suspend reasons, the resource type, the resource name, a description of the resource type that was suspended, the percentage of the region suspend time, and the average suspend time for a transaction.

The CICS Transaction Profile and CICS Region Level reports are produced only if Strobe for CICS with the CICS Transaction Profile option is installed at your site. For more information, refer to the CICS section of the Options-guide.

Strobe for Db2 reports

• SQL CPU Usage Summary shows the distribution of SQL execution in_Db2 CPU activity by DBRM or Query.
• CPU Usage by SQL Statement shows the distribution of SQL execution in_Db2 CPU activity among SQL statements within a DBRM or Query. It displays the DBRM name in the header line, the number of times each statement was executed, and the average elapsed time for the statement calls. The report also identifies sites of invocation by their precompiled statement number.
• SQL Wait Summary identifies the total wait time by DBRM Query.
• Wait by SQL Statement provides detailed information for each SQL statement within a DBRM or Query, including the DBRM name, the number of times each statement was executed, and the average elapsed time for the statement calls.

For more information, refer to the Db2 section of the Options-guide.

Strobe for Db2 DDF reports

• DDF SQL CPU Usage Summary shows the distribution of SQL execution in_Db2 CPU and execution time among DBRMs running in the DDF address space.
• DDF SQL CPU Usage by SQL Statement shows the distribution of SQL execution in_Db2 CPU and execution time among SQL statements in a DBRM running in the DDF address space.
• DDF SQL Statement by DBRM by Requester shows the distribution of SQL execution in_Db2 CPU and execution time among SQL statements in a DBRM from a requester running in the DDF address space. This report can be produced in different formats, depending on the value specified for the requester at the time of installation or at the time a measurement request is submitted. One or two of the following values can be assigned to the requester: location, correlation ID, authorization ID, end user workstation, end user transaction, or end user user ID.

For more information, refer to the Db2 section of the Options-guide.

Strobe for IMS reports

• DL/I CPU Summary shows a summary of all attributed DL/I CPU activity by transaction, module, section, and Program Specification Block (PSB) name.
• DL/I Wait Usage Summary shows a summary of all attributed DL/I wait by transaction, module, section, and PSB name.
• CPU Usage by DL/I Request shows the IMS CPU activity that Strobe for IMS attributed to a DL/I call statement within a transaction, module, section, and PSB name. Each report includes a retrieved segment section and a function activity section.
• The Wait by DL/I Request shows the IMS wait that Strobe for IMS attributed to a DL/I call statement within a transaction, module, section, and PSB name. Each report includes a retrieved segment section and a function activity section.
• The Transaction Utilization Report Summary shows transaction counts and transaction times, ordered by transaction and IMS region, for all regions within the IMS subsystem that was measured.
• The Transaction Utilization Report shows the DL/I activity that Strobe for IMS attributed to the transactions reported by region within the measured IMS subsystem. The report includes transaction counts, module names, PSBs, detail DL/I counts, and performance timings.

For more information, refer to the IMS section of the Options-guide.

Strobe Adabas/natural reports

• Callers’ DB Usage Summary shows the percentage of total CPU activity consumed by each caller of Adabas services. It identifies callers by job name (for a batch job), TSO user ID (for a TSO region), or logical terminal name (for a CICS region).
• Callers’ DB Usage by Control Section appears for each of the database users identified in the Callers’ DB Usage Summary report. The report header line identifies the calling region, and each detail line shows solo and total CPU time spent on behalf of the caller in either an Adabas or IBM system module or in a user-written control section.
• Natural Program CPU Usage Summary shows the Natural programs responsible for CPU activity.
• CPU Usage by Natural Program Statement shows the distribution of the CPU activity among the statements that make up the Natural programs detected by Strobe for Adabas/Natural. The report identifies the use of “INCLUDEd”, or copied, code in a Natural program, indicating the statement number and the corresponding name of the INCLUDE member.

The report also identifies Db2 activity that occurs on behalf of a Natural program, indicating the SQL statement numbers and the DBRM name associated with the Natural program. For Natural for Db2, Strobe produces the CPU Usage by SQL Statement which, together with the CPU Usage by Natural Program Statement, provides in-depth information on SQL statement CPU use.

It also provides information about the IMS database that is being called by a Natural program.

For more information, refer to the Adabas/Natural section of the Options-guide.

Strobe CA-IDMS reports

• Dialog CPU Summary presents a summary of CPU usage by individual CA-ADS/O dialog. The report shows the dialog name, the transaction count and the CPU time.
• CPU Usage by ADS/O Statement details activity within each dialog process and lists the percent total for the entire dialog. The report identifies the dialog name in the header line and sites of invocation by their line number. Because CA-ADS/O dialogs can use “INCLUDEd”, or copied, code, the report adds a suffix, indicating the nesting level of inclusion, to any line number that did not come from the mainline code.

For more information, refer to the CA-IDMS section of the Options-guide.

Strobe for CA gen reports

The Attribution of CPU Wait Time report and the Attribution of CPU Execution Time report are customized to reflect information specific to CA Gen. Strobe produces the following four reports that summarize CA Gen activity:

• Action Diagram CPU Summary shows the distribution of CPU activity among the action diagrams that Strobe identified during the measurement session.
• CPU Usage by Action Diagram Statement shows the distribution of CPU activity among CA Gen statements within a specific action diagram.
• Action Diagram Wait Summary identifies the total wait time by action diagram.
• Wait by Action Diagram Statement provides detailed information for each CA Gen statement within an action diagram.

For more information, refer to the CA Gen section of the Options-guide.

Strobe for Java reports

Strobe initiates a Topaz for Java Performance measurement for applications that run under the Java Virtual Machine (JVM) if Topaz for Java Performance is available on the system. The Topaz for Java Performance report is saved and a link is available from the profile within iStrobe to open the Topaz for Java Performance Report.

If you are using Dynatrace for Java support in Strobe, Strobe optionally initiates a Dynatrace recording session for applications that run under the Java Virtual Machine (JVM) if DynatTrace is available on the system. The Dynatrace report for the time period of the Strobe measurement is saved and a link is available from the profile within iStrobe to open the Dynatrace interface with the save report.

Strobe for WebSphere application server reports

Strobe initiates a Topaz for Java Performance measurement for applications that run under the Java Virtual Machine (JVM) if Topaz for Java Performance is available on the system. The Topaz for Java Performance report is saved and a link is available from the profile within iStrobe to open the Topaz for Java Performance Report.

If you are using Dynatrace for WebSphere Application Server support in Strobe, Strobe optionally initiates a Dynatrace recording session for WebSphere Application Server if Dynatrace is available on the system. The Dynatrace report for the time period of the Strobe measurement is saved and a link is available from the profile within iStrobe to open the Dynatrace interface with the save report.

Strobe for WebSphere MQ reports

Strobeproduces reports that detail WebSphere MQ-related CPU usage and wait time incurred by a batch program. If your installation has Strobe for CICS installed, Strobe for WebSphere MQ also reports on CICS-related service times by WebSphere MQ Queue. Similarly, if your installation has Strobefor IMS installed, Strobe can report IMS transaction-level activity within WebSphere MQ modules.

• WebSphere MQ - CPU Usage Summary shows CPU activity in modules and sections that used WebSphere MQ services.
• CPU Usage by Module by WebSphere MQ for each module shows individual service calls by storage location and, for each storage location, the distribution of calls among queues. If you have Strobefor IMS and you specify the MQTRAN parameter, the report shows this information for each IMS transaction.
• WebSphere MQ - Total CPU Activity by Queue shows a total of CPU activity by WebSphere MQ Queue. This information is provided for all modules in the measured program. The report identifies the percent of CPU attributed to the queue that Strobeobserved during sampling. It also provides data on options associated with the calls.
• WebSphere MQ Messages - CPU Activity by Queue by Module provides data on the various modules that use a given queue and the characteristics of messages associated with that activity.
• WebSphere MQ - Wait Summary shows a summary of the wait time experienced by application modules due to making WebSphere MQ service calls.
• Wait by Module by WebSphere MQ Call for modules with intensive WebSphere MQ activity, shows the individual service calls by storage location. For each storage location, it shows the distribution of calls across queues. If you have Strobefor IMS and you specify the MQTRAN parameter, the report shows this information for each IMS transaction.
• WebSphere MQ - Total Wait by Queue shows a total of wait by WebSphere MQ Queue. This information is provided for all modules in the measured program. The report identifies the percent of run time waiting number for WebSphere MQ calls issued for the queue that Strobe observed during sampling. It also provides data on options associated with the calls.
• WebSphere MQ Messages - Wait by Queue by Module shows total wait by queue and reports on the various modules that use a given queue and the characteristics of messages associated with that activity.
• WebSphere MQ- Service Time by Queue provides CICS transaction wait, execution, and dispatch delay times by WebSphere MQ Queue. This report appears only if you have Strobefor CICS installed, are measuring a CICS WebSphere MQ environment, and have selected to see Region Level CICS reports.
• WebSphere MQ - Summary of CPU Usage by Transaction shows, for each IMS transaction within a WebSphere MQ module, solo and total percentages of CPU usage.
• WebSphere MQ - Summary of Wait Time by Transaction summarizes, for each IMS transaction within a WebSphere MQ module, solo and total percentages of wait time.

For more information, refer to the WebSphere MQ section of the Options-guide.

Strobe for UNIX System Services information

Strobefor UNIX System Services provides information on applications and processes executing in IBM’s z/OS UNIX System Services address spaces. The StrobePerformance Profile is enhanced to show:

• CPU activity and wait time for modules running in z/OS UNIX System Services address spaces
• Use of the Hierarchical File System (HFS) and zFS File System
• Function descriptors for UNIX System Services modules.

For more information, refer to the Unix System Services section of the Options Guide.