Task
The Task page displays information about the performance of each z/OS task in the monitored address space, with the exception of the initiator and dump services.
Menu commands available in this view are as follows:
-
Code Details
Displays the Code Details subpage for the selected task. The activity of the modules and CSECTs running under the task are reported. -
CallerID Details
Displays the CallerID subpage for the selected task. The programs that executed the selected task are reported. -
Delay Details
Displays the Delay Details subpage for the selected task. The delays associated with the selected task are reported.
TaskView provides information about the components of the monitored address space. When you TAG one or more Tasks, then use the SELect command
Contents:
Task Columns
The Task page contains the following columns:
-
Program
The name of the program attached by the initiator or another lower level program. This name is always the target of the ATTACH macro. -
Active %
The percentage of the monitored period that a CPU was actively processing the task. -
Data %
The percentage of the monitored period that the task was delayed because of an I/O request. -
System %
The percentage of the monitored period that the task was busy executing system functions such as memory management or security control. -
VolWait %
The percentage of the monitored period that the task waited voluntarily. The value in this field does not include wait time related to data delay. -
InvWait %
The percentage of the monitored period that the task waited because one of the following situations occurred:-
The address space was swapped out and unable to run
-
The address space was swapped in, but was not given control of the CPU
-
-
Other %
The percentage of the monitored period that the task waited for events not included in other fields. Events such as dispatcher waits, swap delays, and paging delays are included in this field. -
Total %
The sum of the six delay categories, reflecting the total percentage of delay for this task.
Delay Details
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. Double-click the particular line, select the Delay Locations command or switch to the CodeView to see which modules have the highest CPU usage. -
Voluntary
The program has voluntarily Wait relinquished control of a CPU. Double-click the particular line or select the Delay Locations 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, select the Delay Locations command or switch to the DataView 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, select the Delay Locations command or switch to the CodeView to see which modules have the highest CPU usage. -
File
The program is delayed by a file Management 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.