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

DFSDLOC0

DFSDLOC0 is the DL/I Database Open/Close module. It opens and closes all database datasets and primary and secondary indices. DFSDLOC0 can be invoked from several places including the DL/I call analyzer DFSDLA00, DL/I retrieve DFSDLR00, and DL/I delete/replace DFSDLD00.

DFSDLOC0 not only opens the dataset DCB/ACB, it also loads the randomizer, segment edit compression routines, and secondary index maintenance routines. Control blocks are valued with database information, datasets are assigned to OSAM or VSAM buffer pools, and other modules are called for DBRC, lock management, and dataset use indicator (DUI) processing. Special processing is also done for data sets opened for load.

For database close processing everything is undone. The data set is closed, the randomizer and routines are deleted, fields are valued, and other modules are called to process data set close. DFSDLOC0 will also initiate the purge of all buffers for the data set.

Hints

The proportion of CPU used by DFSDLOC0 should be very small. There is one performance consideration for database open/close. If the pool that holds the database control block (DMB pool) is too small, an unused database might be closed to make room for a database just referenced whose control block is not in the pool. Many database opens and closes can occur as databases vie for space in the pool. Examine the IMS log for type x'20' (open) and x'21' (close) log records for a history of the database opens and closes.

Reference Sources

More information is available in the IMS DBSOURCE Library Data Set. See your IMS systems programmer.