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

MQSeries Activity by Transaction by Call

The MQSeries Activity by Transaction by Call report is generated when a Strobe measurement includes online IMS data. For each queue manager, it shows MQSeries CPU activity caused by IMS transactions in MQSeries modules, and run time spent in wait experienced by IMS transactions in MQSeries modules.

If the MQTRAN parameter was specified when the Performance Profile was created, the report shows the distribution by queue over transactions within a queue manager for measured modules, control sections and offsets.

Report details

Queue Manager shows the name of a queue manager.
CPU % Total: MQSeries activity with or without any such concurrent activity
Wait % Page: wait time that results from retrieving a page from the page data set. A high value in this column indicates that there is not enough physical memory assigned to the address space. If you noticed a high paging rate on the Measurement Session Data report, the Wait Time by Module report enables you to see which module was experiencing delay because of paging.
Wait % Total: all causes of wait time, including page retrieval, programmed I/O operations, and timer requests.

Click next to the queue manager to view additional detail:

Transaction shows the name of a transaction.

If the MQTRAN parameter was specified, click next to the Transaction to view additional detail:

Module shows the name of the active module.
Section shows the name of the active section.

Click next to the Module to view additional details:

Request location shows the offset from which the request was initiated.
MQSeries call shows the name of the call.

Click next to the Request location to view the Queue.