Transaction summary report

The Transaction Summary report shows the distribution of CPU usage among transactions processed by the target subsystem. Strobe produces the report when it encounters transaction identifiers in the sample data set. The report lists transactions in ascending order by transaction identification code. This report enables you to identify transactions that use a great proportion of CPU resources. It also guides you to control sections shown in the Transaction-usage-by-control-section-report when you suspect that a transaction’s use of resources is high for its frequency or value.

When you measure a CICS region and produce the CICS Performance Supplement, Strobe expands the Transaction Summary report and places it in the CICS Performance Supplement. For a description of the expanded report, refer to the CICS section of the Using-Strobe-options.

When you measure an IMS Message Processing region (MPR) or CA-IDMS online region, Strobe expands the report, adding columns for transaction counts and average service time. For a description of the expanded report, refer to the IMS or CA-IDMS section of the Using-Strobe-options.

Transaction Summary Report

Each transaction appearing in the Transaction Summary report is treated in greater detail in Transaction-usage-by-control-section-report.

NAME

A transaction, pseudo-transaction, or function name supplied by a data collector program. If the name contains unprintable characters, Strobe shows it in hexadecimal notation.

The transaction identifier. If the name is not alphanumeric, it is shown in hexadecimal notation. The following types of transactions are reported:

- User transaction - A user-defined transaction that executes user written programs
- System transaction - A CICS-supplied transaction that provides internal services or access to CICS resources. (System transaction always begin with C and sometimes do not have counts associated with them. Mean service time does not appear for system transactions.)
- Mirror transaction - A CICS-supplied transaction that acts on behalf of the initial user transaction that was executed on a remote system.
- Strobe for CICS associates execution activity with user and CICS system transactions. When Strobe for CICS detects activity in the main CICS task and neither a user nor a CICS system transaction is in control, it assumes that CICS is performing activities on its own behalf and it attributes that time to a pseudo-transaction named .CICS.

When a task other than the main CICS transaction-processing task is executing, Strobe for CICS attributes the CPU time to a pseudo-transaction that is assigned a name consisting of an initial period, and the first seven characters of the module name in which execution of the task was initiated. The Strobe CICS journaling task and asynchronous VSAM task are attributed using this convention.

When a task is initializing or terminating and Strobe for CICS cannot identify the name of such a module, activity is attributed to the pseudo-transaction .NOPRB.

PROFILED

The letter Y in this column indicates that a transaction detail report was created for the transaction. You can request a detail report for a specific transaction by specifying the transaction name in the CICS TRANSACTION PROFILING FILTER field of the Strobe - Tailor Report panel. If you do not specify any transaction filters on the Strobe - Tailor Report panel, detail reports are created for the transactions you specified on the Strobe- CICS Data Collector Options panel when you submitted the measurement request.

COUNT

The number of times a transaction was executed during the measurement session.

CPU TIME PERCENT

The total percent of all CPU time consumed in the CICS region for all transactions, which was used by the transaction.

Important

If a transaction was attached prior to the start of the measurement session and still active at the end of the session, the reported service time may be less than the actual service time for the transaction. For conversational transactions, the average total time the transaction is active during the measurement was reported.

MEAN SERVICE TIME: DISPATCH DELAY

The average number of seconds when a transaction is ready to run but is waiting to be dispatched.

MEAN SERVICE TIME: SUSPEND

The average number of seconds that a transaction is waiting on a resource before being able to be dispatched.

MEAN SERVICE TIME: EXECUTE

The average number of seconds that a transaction is running.