Delay analysis monitors and views

The time that transactions spend waiting for resources or events can significantly impact CICS performance.

Reducing these delays is an important part of tuning your CICS region for optimal performance. The solution to system performance problems can become clearer with a full understanding of why transactions are forced to wait.

The MainView for CICS delay analysis functions provide a statistical sampling of the reasons that tasks are suspended. The reasons that tasks can be delayed are divided into 27 groups, such as DB2 waits, file control waits, interval control waits, etc. These groups are further categorized by resource type and resource. The delay analysis functions collect data on the number of tasks waiting for each resource at each sample and provide views to interpret the results.

Delay related data is collected by the delay analysis monitor. The delay analysis monitor collects data based on an analysis definition. The data is archived based on the IRRI interval period as set in the BBIISP00 parameter member. Each interval is divided into 10 discreet sub-intervals.

The basic delay analysis data point consists of a suspended resource and the count of tasks waiting on it at the time the sample is taken. CICS suspend resources are categorized by suspend type and suspend group. Each suspended resource consists of three levels of identification:

  • resource group
  • resource type
  • resource name

Many resources have fixed resource names, while others have variable names. Files, for example, use the name of the file causing the delay.

Resource-groups-and-resources-monitored-by-delay-analysis-monitor lists the resource groups and resources that can be monitored.

This section describes the MainView for CICS delay analysis monitors and views:




 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*