Delay Details
The Delay page provides details in the following columns:
-
Major Category
CA MAT divides the monitored program's activity and delays into the following major categories. These categories account for 100 percent of the elapsed time during the monitored period-
Program
The program (or one of its Active subroutines) is in control of a CPU. -
Voluntary
The program has voluntarily Wait relinquished control of a CPU. Use the A (Analyze) line command to determine the delay locations within the application. -
Abend
A component of the application is Procedure terminating abnormally or Delay gathering diagnostic information for a problem. Double-click the particular line or select the Delay Locations command to determine where the program invoked the abend procedures. -
Data Delay
The program is waiting for data to be returned. Double-click the particular line or select the Delay Locations command to see which files caused the greatest delay. -
Resource
The program is delayed because Conflict another program has exclusive use of a required resource, such as a file or program. Double-click the particular line or select the Delay Locations command to determine which modules spent time waiting for resources. -
System Active
The program is using operating system functions, such as storage administration or system security. Double-click the particular line or select the Delay Locations command to see which modules have the highest CPU usage. -
File
The program is delayed by a file management operation such as Delay locating or opening a file. Double-click the particular line or select the Delay Locations command to determine which modules spent time waiting for file management activities. -
Program Load
The program is delayed by the Delay operating system while it performs program management functions. Program management functions include locating a program on DASD, obtaining storage, reading the program, or converting the relative addressing information into absolute addresses. Double-click the particular line or select the Delay Locations command to determine which modules spent time waiting for program load activity. -
DASD
The program is delayed because of Management a DASD file management function Delay that is not part of normal file management. Double-click the particular line or select the Delay Locations command to determine which modules spent time waiting for DASD management functions. -
CICS Delays
The CICS susbsystem delays are divided into the following categories:-
CICS System Delay
-
CICS TransData
-
CICS StorCtl Delay
-
CICS TaskCtl Delay
-
CICS TransData
-
CICS StorCtl Delay
-
CICS TaskCtl Delay
-
CICS FileCtl Delay
-
CICS JourCtl Delay
-
CICS TempStor Delay
-
CICS ProgCtl Delay
-
CICS TermCtl Delay
-
CICS DL/I Delay
-
-
Other Delays
The program is delayed for a reason not listed in this table. These delays may be related to paging, swapping, or non-dispatching.
-
-
Minor Category
Displays the subcategories of program activity or delay within each major category. -
Active %
The percentage of time for a monitored period when CA MAT detected a task to be executed on a CPU. -
Wait %
The percentage of the monitored period that the delay category was not executing on a CPU. The value in this field includes both voluntary and involuntary wait. The wait is voluntary if the code was waiting for a particular time or event before executing. The wait is involuntary if the code is ready to execute, but is not in control of a CPU. This type of wait may be caused by the execution of higher priority programs in the system. -
Total %
The sum of both the Actv% and the Wait% columns.