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

DFSZSC00

The program request handler invokes DFSZSC00 to process IMS extended checkpoint calls. An extended checkpoint call is a checkpoint call (CHKP) that begins with an extended restart (XRST) call.

DFSZSC00 logs database positioning, including GSAM, and user data areas in type x'18' log records. It scans each database and GSAM PCB in the PSB to see if there is a position to log. Then it logs up to seven user areas passed in the CHKP.

Hints

The amount of CPU used by DFSZSC00 (and the amount of data written to the IMS log) depends on the checkpoint frequency, the number of database and GSAM PCBs to scan and log, and the number and size of the user data areas to log.

Checkpoint frequency depends on the application, but it is possible to take checkpoints too frequently and use unnecessary resources. If this is a BMP job and checkpoints are taken to free resources and commit databases, and not for restart purposes, then use the SYNC call instead of the CHKP call. The SYNC call provides all of the database integrity with much less overhead than the CHKP calls. Type x'18' log records are not created and application checkpoint messages are not sent to the MVS system log.

The number of PCBs and user data areas also depends on the application. Monitor them to ensure they are being used efficiently.

Reference Sources

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