Delay

The Delay page shows program elapsed time broken down by types of delays.

The Delay page divides the program into functional delay types. Delay types comprise everything that contributes to the elapsed time of the program, including the time that the program was executing.

Note: See Analyze Application Delays in the CA Mainframe Application Tuner product documentation for a comprehensive list of delay types that are identified by the Delay analysis option.

Menu commands available in this view include:

Contents:

Delay Columns

The Delay page has the following columns:

  • Major Category
    CA MAT divides the activity and delays of the monitored program 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 line or select the Delay Locations command 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 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 that is 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.

Delay Locations: Delay Type Program Active

  • Module
    Displays the name of the module where the delay occurred.

    Note: Module names which contain a dash - ABCDE-01- indicate a USS or Java Longname. The right-most portion of the longname is included in the Description field. Use the N line command to display the full name.

    Module name *PATHNAM indicates an HFS load module who's name was not able to be resolved (there is no associated longname).
    Module names in the format .XMSnnnn indicate resolved (there is no associated longname).
    Module names in the format .XMSnnnn indicate an address space (not a module). The .XMS prefix indicates cross-memory services are currently being accessed. The nnnn portion of the name is the hexadecimal number of the address space. In this case, the Csect field displays the name of the address space.
    Module names in the format .Snnnnnn indicate the program activity occurring in the generated DB2 code that is bound with the DBRM. The CSECT name is the name of the DB2 address space where this is executing.

  • Csect
    Displays the name of the Csect where the delay occurred.

    Note: If the module name is in the format .XMSnnnn, this name is the name of the address space that the application is accessing through cross-memory services.

  • Offset
    Displays the hexadecimal offset from the start of the Csect where the delay occurred.
    For .USER, .EUSER, .COMMON, and .ECOMMON, this is the virtual address of the delay and not an offset.

  • D
    Displays Y when details are available for the delay at this location, and the D (Details) line command is valid.

  • C
    This field contains a Y if Callerid information is available for this Csect. Callerid provides detailed information about which programs called the Csect being queried.
    For the subroutine of a High-Level Language, such as COBOL, Callerid can help determine how to correct the problem.

    Note: Even though much care is taken to ensure accurate information, Callerid may not always be accurate. Sometimes it is not possible to obtain precise information. When presented with a calling module that does not make sense, you must ask yourself if the call would be possible.

  • X
    This field contains a Y if LE Callerid information is available for this Csect. Extended (LE) Callerid provides detailed information about which programs called the Csect being queried.

  • Pct %
    The percentage of the monitored period that activity was detected at this location.