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

DFHTSP

DFHTSP is the CICS temporary storage control program that services EXEC CICS READQ, WRITEQ, and DELETEQ requests. It maintains the tables, directories, and maps needed to keep track of temporary storage records and available space on VSAM auxiliary temporary storage, or in main temporary storage.

Hints

Change CICS to have main temporary storage, and put main temporary storage above the 16 megabyte line. This immediately recalls storage. If storage needs to be recalled from disk, the operating system paging routines are more efficient than CICS temporary storage routines. To do this, instead of writing temporary storage exit (XTSREQ), utilize the SIT parameter TS=(COLD,0).

This technique eliminates temporary storage I/O, improves response time, and saves DASD space because the temporary storage data set can be deleted.

If there is high wait for DFHTSP on the Resource Demand Distribution report, main storage rather than auxiliary temporary storage should be used. If I/O activity to DFHTEMP is high on the Data Set Characteristics report, a lot of auxiliary temporary storage is used. Change to main storage because main storage does not use as much CPU as auxiliary storage. Also if a lot of auxiliary storage is used, the Program CPU Use report will show high CPU usage to DFHTSP.

In the Strobe CICS Performance Supplement, the Configuration Parameters and System-Wide Statistics report will show information in the Temporary Storage Statistics report.

If the STAE option run-time COBOL option is specified, excessive temporary storage may be used. If STAE is specified, dump output will be generated. If NOSTAE is specified, there will be no dump. From a COBOL standpoint there is no preferred option, but with CICS you may want to note that the dump output is directed to the temporary storage queue.

High CPU in DFHTSP may be the result of spanned record processing. A spanned record is a record whose size exceeds the control interval size in DFHTEMP. Reads and writes of spanned records cause recursive calls to DFHTSP.

Reference Sources

CICS/MVS Version 2.1 Diagnosis Reference, LC33-0517.

CICS Tuning and Performance, Xephon Consultancy Report, August 1991.

IBMLINK: Q585210

IBMLINK: RTA000036049