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

IEFRDER*

IEFRDER is an IMS log card that updates a database in a DL/I region. IEFRDER is often forced to be undummied in a database recovery control region (DBRC), but can be suppressed if a job step declares how to update a database. With IMS 1.3, DASD logging replaced the tape logging facility. IEFRDER and IEFRDER2 might now be a combination of tape and DASD.

The DASD logging facility requires two types of files: the On-Line log Data Set (OLDS) and the Write Ahead log Data Set (WADS). The OLDS file is basically analogous to the tape log. The WADS file replaces and enhances features provided by former IMS disk logging facilities.

Hints

WADS is a critical data set and should be placed on dedicated packs on strings without access problems and on very high performance DASD. Do not allocate these data sets on cached DASD devices.

On the Resource Demand Distribution report, the number of I/Os to IEFRDER appears in the EXCP column. Update calls are expensive if IEFRDER is undummied as DBRC often requires. The Percentage of Runtime Causing CPU Wait column shows the percentage of wait caused by that file. If wait is a high percentage and IEFRDER is on DASD rather than tape, look at the cylinder detail on the I/O Facility Usage report and determine if the calls are primarily random (many Get Uniques [GU]). If the calls are primarily random, adding buffers might help.