Tuning Your Applications › Overview of Delay Categories

Overview of Delay Categories

In CA MAT, autonavigation enables you to go directly from a delay category to a more detailed panel that provides relevant information about the delay. This section presents an overview of delay types, with recommendations about how to use CA MAT to find out more about why your job is experiencing a delay.

Program Active

The program or one of its subroutines is in control of a CPU.

Place your cursor anywhere on the line and press Enter, or select Option 3 to see which modules have the highest CPU usage.

Voluntary Wait

The program has voluntarily relinquished control of a CPU.

Use the Address line command (A) to determine the delay locations within your application.

Abend Procedure Delay

A component of the application is terminating abnormally or gathering diagnostic information for a problem.

Use the Address line command (A) to determine where the program invoked the abend procedures.

Data Delay

The program is waiting for data to be returned.

Place your cursor anywhere on the line and press Enter, or select Option 5 to see which files caused the greatest delay.

Resource Conflict

The program is delayed because another program has exclusive use of a required resource, such as a file or program.

Use the Address line command (A) 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.

Place your cursor anywhere on the line and press Enter, or select Option 3 to see which modules have the highest CPU usage.

File Management Delay

The program is delayed by a file management operation such as locating or opening a file.

Use the Address line command (A) to determine which modules spent time waiting for file management activities.

Program Load Delay

The program is delayed by the operating system while it performs program management functions.

Program management includes locating a program on DASD, obtaining storage, reading the program, or converting the relative addressing information into absolute addresses. Use the Address line command (A) to determine which modules spent time waiting for program load activity.

DASD Management Delay

The program is delayed because of a DASD file management function that is not part of normal file management.

Use the Address line command (A) to determine which modules spent time waiting for DASD management functions.

CICS Delays

The CICS subsystem delays are divided into the following categories:

• CICS System 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 section.

These delays can be related to paging, swapping, nondispatching, or other reasons.