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

DFSISI00

DFSISI00, the IMS Subsystem Interface, has two different functions: it provides MVS Subsystem Interface (SSI) support and it is also the online program request handler when DFSPR000 is in batch.

As an MVS subsystem, IMS is informed by MVS of various events. Examples include MVS commands, such as CANCEL JOB xxx, which DFSISI00 will nullify if xxx is an IMS dependent region. Another example is task abnormal terminations, which will cause DFSISI00 to invoke IMS backout if the failing job is an IMS dependent region. DFSISI00 also processes subsystem requests from IMS dependent regions such as Identify, Sign On, and Create Thread, which establish the communication between the dependent region and the IMS control region.

Upon return from whichever path processed the call, DFSISI00 calls DFSECPxx for a second pass, invokes the Data Capture Exit routine if required, and then returns directly to the application program.

Hints

The resources DFSISI00 uses are only partly influenced by IMS and its application programs. The subsystem interface routines are driven by MVS events. The busier the MVS system, the more work DFSISI00 will have to do.

From an IMS point of view, DFSISI00 is driven by call volume. There is slightly more overhead for the AIB interface than the standard interface. The AIB interface should only be used where it is not possible to use the standard interface, as in a Data Capture Exit routine.

Reference Sources

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