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

DFSECP20

DFSECP20 is the BMP Environment Control Program. Some functions, checkpoints, restarts, and GSAMs are processed all or in part by modules in the BMP region, as opposed to the IMS DL/I or Control Regions. DFSECP20 is the interface to these modules.

DFSECP20 is invoked by the program request handler DFSPR0X0. If the call is an XRST call and is a restart request, the extended restart module DFSZSR00 is invoked. If the call is a CHKP or SYNC call, the GSAM controller DFSZDC00 is invoked. If the call is an extended checkpoint, the extended checkpoint module DFSZSC00 is then invoked. If the call is for a GSAM PCB, the GSAM controller DFSZDC00 is invoked. All of these modules are in the BMP region. Control then returns to the program request handler.

DFSECP20 has one other function. If the NOSPIE option has been specified in the BMP PARM, DFSECP20 deletes any user SPIE. This module is also invoked by the program request handler for a second pass after the call is completed; if there was a user SPIE it will be restored.

Hints

DFSECP20 should not normally be a significant user of CPU in an IMS BMP job. There are two exceptions:

If the frequency of checkpoints is high, some CPU will be used in this module.

There is the potential for significant CPU use when the NOSPIE PARM is specified, the calling application has a user SPIE, and the calling application makes a large number of DL/I calls. The CPU use in this module and in SVC 109 could be considerable. Check to see if it is possible to remove the SPIE from the application, or to remove the NOSPIE parm and have the application handle the SPIE condition.

Reference Sources

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