Application Audit Online Help
Compuware Enterprise Services
Fault Analytics
ISPW Web Interface
ThruPut Manager Web
Topaz For Java Performance
Topaz for Total Test Web Client User Guide
- Welcome to Topaz for Total Test
- Topaz for Total Test Non-virtualized Test Overview
- Getting Started
  - Getting Started Tutorial
  - Using the Web Client
  - Create a Test Suite from Browser
- Test Virtualization
  - Test Virtualization
  - Stubs in the Web Client
  - Recording Input Data to Sub Modules
- Extending Non-virtualized Test with Custom Data Definitions
- Code Coverage
- Configuring the Topaz for Total Test Repository Server
- Working with the Repository
  - Working with the Repository
  - General Information for All Artifacts
  - Defining and Using Components
  - Components in the Web Client
  - Connections
  - Environments
  - Systems
  - Categories
  - User Groups
  - Skins/Data and Execute
  - Stubs
  - Job Definitions
  - Dataset Skins
  - Test Scenarios
  - Suites
  - Reports
- Sample Programs
- Appendix A Tutorial Add a Component to the Repository with the Web Client
- Welcome to Topaz for Total Test
- Get a License
- Topaz for Total Test Functional Test Overview
- Getting Started
  - Getting Started Tutorial
  - Using the Web Client
  - Create a Test Suite from Browser
- Test Virtualization
  - Test Virtualization
  - Stubs in the Web Client
  - Recording Input Data to Sub Modules
- Extending Functional Test with Custom Data Definitions
  - Extending Functional Test with Custom Data Definitions
  - Extending a Test Scenario
  - Extending the Execution Context
- Code Coverage and IDz Integration
  - Code Coverage and IDz Integration
  - Browser Client
  - Eclipse Client
- Utility Tools
  - Utility Tools
  - Environment Specific Host UserIDs
  - Management Of Saved Host Credentials
  - Browse Datasets
  - Get Job Info and Spool Files
  - Copy And Delete Datasets
- Configuring the Topaz for Total Test Repository Server
  - Configuring the Topaz for Total Test Repository Server
- Working with the Repository
  - Working with the Repository
  - General Information for All Artifacts
  - Defining and Using Components
  - Components in the Web Client
  - Connections
  - Environments
  - Systems
  - Categories
  - User Groups
  - Skins/Data and Execute
  - Stubs
  - Job Definitions
  - Dataset Skins
  - Test Scenarios
  - Suites
  - Reports
  - Schedules
- Sample Programs
  - Sample Programs
  - Program XAPGMTST
  - Program XADB2TST
  - Program XAMOCTST
  - Program XAPGMCAL
  - Program XAPGMBT1
  - Program XARISCAL
  - Program XADTSTMP
  - Program XADGTIME
  - Program XADUTF8
iStrobe Online Help

CPU Usage by C/C++ Function

The CPU Usage by C/C++ Function report shows the distribution of CPU time used by each active control section of each module in the target program or subsystem.

CPU time used by each control section is given as a percentage of all CPU time used in the measured job step. The CPU time percentages used by all listed control sections reflect only the C/C++ control sections that have been identified by Strobe. The time used combines both the execution and attribution percentages.

If the control section was not indexed, the report shows activity within a code block, an area whose size in bytes is equal to the report resolution specified when creating the Performance Profile. Each code block is identified by its starting location and its length.
If the program was indexed, the report shows activity within procedure boundaries dictated by C/C++

Source support is not provided for those application programs that have not reached the Detail Baseline or where the source is not provided.

Report details

Module is the name of the module for which Strobe is detailing CPU usage.
CPU % shows the percent of CPU time (execution and attribution) used by the module, section, or function.
Total shows activity with or without any concurrent I/O activity.

Click next to the Module to view additional detail:

Section is the name of the CSECT within the module for which Strobe is detailing CPU usage. Class information includes both the Strobe token of the name and the "long" name.

Click next to the Section to view additional detail:

Function is the name (or token name) of the function within the section for which Strobe is detailing CPU usage. If the token name is provided, then the actual name can be found in the Token-longname Cross Reference report.

Click arrow next to the Function to view additional detail about the C/C++ statement:

Starting location shows the location by offset within the module, class, or function at which Strobe detected activity.
Number shows the line number of the C/C++ that corresponds to the offset within the module, class, or method at which Strobe detected activity, for indexed programs.
Text shows the text of the C or C++ statement that corresponds to the starting location and line number at which Strobe detected activity, for indexed programs.