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

DSNIOSET

DSNIOSET is part of internal processing for Performance Trace events. It records input to matching and non-matching index scans for the IFCID 15 records. The IFCID 15 record provides information about the type of Index scan performed. If the scan type is non-matching, (also indicated by MATCHCOLS=0 in Explain), this module may show a significant amount of overhead since the entire index has been scanned. When MATCHCOLS > 0, the Index tree is used for initial position access, and the Leaf pages are then scanned forward from that position. The higher the number of columns in MATCHCOLS, the lower the usage of this module will be. The IFCID 18 record is written at close or re-use of a Cursor Usage Block (CUB), end of file, or no record found conditions. This module will only show usage if performance trace classes are active.

Hints

Proportionally large amounts of time within this module may indicate an index scan. Evaluate the application SQL using EXPLAIN. If MATCHCOLS is zero, a full index scan is performed. If MATCHCOLS is greater than zero, but less than the number of columns in the index, and the Index tree is used for access, then some number of leaf pages will be scanned forward to locate all qualifying RIDs.

Proportionally large amounts of time in this module also occur with the repetitive execution of indexed access with a high number of MATCHCOLS. If a large amount of time is attributed to DSNVSR for this statement and the statement is not using an INDEX ONLY, evaluate the possibility of replacing synchronous I/O with set processing.

For high volume insert activity, ensure that the inserted rows are sorted into the sequence of the clustering index.

Reference Sources

IBM Db2 for OS/390, Messages and Codes, GC26-8979