How impact analysis works

Impact analysis monitors selected CICS® regions at periodic intervals and determines which of the following three execution states categorize each observation.

Productive: CICS is performing useful work, such as using CPU or performing I/O.
Unproductive: CICS is ready but unable to perform work. If CICS must wait for an MVS resource that another address space is using, that address space is said to be contending with CICS. Impact analysis shows it as affecting CICS performance. When CICS is unproductive, impact analysis identifies the specific address spaces that are using the resources for which CICS is waiting. Examples of unproductive states are CPU dispatching waits and time spent queued for I/O. This option displays as Contention.
Other: CICS is not performing work due to normal reasons. OMEGAMON for CICS (3270) disregards these states, since they do not indicate performance degradation. This option is not shown in impact analysis displays. Waiting for work and STIMER are examples of idle states.

After activating the impact analysis collector, allow accumulation of enough intervals (at least 30), so that the data displayed is statistically valid.