Workload/monitor issues

How well are my workloads performing?

The COBJ view shows the average response (elapsed) time for the IBM CICS transactions in a workload that occurred in each interval. The date on whether the workload is meeting its defined goals is represented numerically and graphically. This is an historical view that can be used in conjunction with the TIME command to show workload data over a substantial period of time

How much of the response time of my workloads is spent waiting for resources?

The CFLOW view shows the percentage of the average response (elapsed) time for the CICS transaction in a workload that was spent waiting for resources (delay). This data is represented numerically and graphically. Additionally, it also displays the primary reason for delays. This view is an historical view that can be used in conjunction with the TIME command to show the workload data over a substantial period of time.

Why are components reported in the average response times for my workloads?

The CWOVER view shows the average response (elapsed) time for the CICS transaction in a workload and the percentage of that time that was spent accessing the various types of resources. This data includes information such as the CPU time, dispatch wait time, file control time, and so on. This is an historical view that can be used in conjunction with the TIME command to show the workload data over a substantial period of time.

How do I create a workload?

Workloads are defined by using the CWKLDDEF view. The definitions can be used to start monitoring particular CICS regions for a specific period of time. The definitions can be configured to restrict the workload to particular transactions, programs, files, and so on and provides the ability to set response time goals and a required percentage of transaction that must meet that goal. Workload definitions can be installed on a CICS region from this view.

How can I determine the historical trend for delays affecting the response times of transactions executing on a CICS region?

The CDELAY view provides CICS delay analysis showing the number of tasks that have waited on particular resources during the sampling interval. The sampling interval matches the time interval that is used by the CREGION record and is similarly broken down into ten sub-intervals for greater granularity. The delays can be summarized by groups by using the CDELAYGZ view or by types using the CDELAYTZ view.

How do I create a delay analysis monitor for use by the CDELAY views?

Delay analysis monitors are defined by using the CDLYDEF view. The definitions can be used to start monitoring particular CICS regions for a specific period of time during the day. The definitions can be configured so as to restrict delay tracking to particular resources or resource groups. Additionally, both system transactions and specific transactions can be excluded. Monitor definitions can be installed on a CICS region from this view.

How can I see what delay analysis monitors are running on a CICS region?

The CDLYACT view shows the current active delay analysis monitors for a CICS region. Delay analysis monitors that are no longer required can be stopped or purged from this view.

Without setting up a full-blown monitor, how can I determine what resources are causing delays currently experienced by the tasks executing on a CICS region?

The CRDELAY view provides real-time CICS delay analysis data that is sorted within individual regions by the number of tasks that are waiting on a particular resource name. The delays can be summarized by groups by using the CRDLAYGZ view or by types using the CRDLAYTZ view.