Help

Contents
Search

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

Percent of Run Time Causing CPU Wait

Percent of Run Time Causing CPU Wait is the percentage of run time during which execution was delayed pending the occurrence of an awaited event, usually an I/O completion event.

For a task execution activity, % Run Time Causing CPU Wait represents the time during which execution for the measured job step was blocked while an event not associated with any particular file access was completed. In the case of online subsystems, this time is most commonly simple terminal I/O wait--wait incurred because there are no transactions to process. Other factors that might contribute to wait time reported in .FILEMGT execution activity include module loading, inter-region communication, and timer requests. Time spent waiting for completion of any of several file access operations--a multiple wait condition--is included in a task line entry if the module in which the wait occurs is not a standard access method module. Normally, you cannot reduce this percentage of wait time.

For file access activities, % Run Time Causing CPU Wait represents the time during which execution in the measured job step is blocked while waiting for an I/O operation to finish. This value includes the time during which the activity was enqueued because of contention in the system for the required I/O facility. It does not include time spent waiting for data sets to be opened. (Such activity is reported in .FILEMGT.)

If other active address spaces are contending for the required I/O facility, the activity might be delayed while I/O requests are enqueued prior to the initiation of I/O operations. The report shows the delay in an excessive CAUSING CPU WAIT value. If the target program or subsystem achieves a high degree of overlap of two or more I/O activities but does not use much CPU time, the % Run Time Causing CPU Wait value will be higher than that of % Run Time Solo in I/O. This preponderance usually signifies efficient management performance.

Time spent waiting in a standard access method module for the occurrence of one of several events--for example, for the completion of open and close operations--is ascribed to .FILEMGT.

More about the Resource Demand Distribution report