The Wait Analysis report prints details per control break. Each
BY sort field combination causes a control break in the report.
Figure 1 shows part of the Wait
Analysis report and
Figure 1 shows
the Wait Analysis Recap report produced by the command:
CICSPA WAITANAL(OUTPUT(WAIT0001),
INTERVAL(00:01:00),
BY(TRAN,APPLID))
Figure 1. Wait Analysis
report V5R1M0 CICS Performance Analyzer
Wait Analysis Report
WAIT0001 Printed at 15:49:47 11/23/2012 Data from 11:19:50 10/11/2012 to 11:25:08 10/11/2012 Page 1
------------------------------------------------------------------------------------------------------------------------------------
Tran=FTST APPLID=IYCUZC20
Summary Data -------- Time --------- ------ Count ------ ------ Ratio ------
Total Average Total Average
# Tasks 6204
Response Time 11.8997 0.0019
Dispatch Time 3.3065 0.0005 121774 19.6 27.8% of Response
CPU Time 1.7015 0.0003 121774 19.6 51.5% of Dispatch
Suspend Wait Time 8.5932 0.0014 121774 19.6 72.2% of Response
Dispatch Wait Time 5.3776 0.0009 115570 18.6 62.6% of Suspend
QR TCB Redispatch Wait Time 3.6745 0.0006 78341 12.6 68.3% of Dispwait
Resource Manager Interface (RMI) elapsed time 0.0000 0.0000 0 0.0 0.0% of Response
Resource Manager Interface (RMI) suspend time 0.0000 0.0000 0 0.0 0.0% of Suspend
Suspend Detail ------------------- Suspend Time ------------------- ----- Count -----
Total Average %age Graph Total Average
DSCHMDLY Redispatch wait time caused by change-TCB mode 3.7917 0.0006 44.1% |******** 74448 12.0
LMDELAY Lock Manager (LM) wait time 1.7913 0.0003 20.8% |**** 15889 2.6
TCIOWTT Terminal wait for input time 1.2096 0.0002 14.1% |** 24816 4.0
DSPDELAY First dispatch wait time 1.1863 0.0002 13.8% |** 6204 1.0
JVMTHDWT JVM server thread wait time 0.6143 0.0001 7.1% |* 417 0.1
------------------------------------------------------------------------------------------------------------------------------------
The Wait Analysis report has two sections:
- The first section provides a summary of common performance metrics,
including:
- Number of tasks
- Response time
- Dispatch time
- CPU time
- Suspend wait time
- Dispatch wait time
- QR TCB Redispatch Wait Time
- RMI elapsed time
- RMI suspend time
- The second section provides a detailed breakdown of Suspend time
by component, such as Dispatch wait, File wait, and so on. Components
are reported in descending wait time order, thereby ensuring that
the primary cause of task wait is at the top of the list.
Only
wait clocks with non-zero elapsed time are reported.
BY sort fields
You can select up to three
BY sort fields. If one of the BY fields is a Start or a Stop time,
the Interval specification is also reported. If a field is
not present in the SMF input records, a value of <Missing> is
reported. Missing values are always shown after values that are present.
Summary Data
The column headings in this
part of the Wait Analysis report are:
- Time
-
- Total
- Total elapsed time.
- Average
- Average elapsed time (Total divided by #Tasks).
- Count
-
- Total
- Total number of events.
- Average
- Average number of events (Total divided by #Tasks).
- Ratio
- Percentage of time this component contributed to overall Response,
Dispatch or Suspend time. Ratios are calculated using the values in
the Total Time column.
The row information includes:
- # Tasks
- The total number of tasks.
- Response Time
- Task Response time, calculated as Stop time (owner: DFHCICS, field
ID: 006) minus Start time (owner: DFHCICS, field ID: 005).
- Dispatch Time
- The total elapsed time during which the user task was dispatched
by the CICS® dispatcher domain
on each CICS TCB under which
the task ran (field: USRDISPT, owner: DFHTASK, field ID: 007).
- CPU Time
- The total processor (CPU) time during which the user task was
dispatched by the CICS dispatcher
domain on each CICS TCB under
which the task ran (field: USRCPUT, owner: DFHTASK, field ID: 008).
- Suspend Wait Time
- The total elapsed suspend (wait) time for which the user task
was suspended by the CICS dispatcher
domain (field: SUSPTIME, owner: DFHTASK, field ID: 014).
- Dispatch Wait Time
- The elapsed time for which the user task waited for redispatch
by the CICS dispatcher domain
(field: DISPWTT, owner: DFHTASK, field ID: 102). This is the aggregate
of the wait times between each wait event completion and the user
task being redispatched by the CICS dispatcher
domain.
- QR TCB Redispatch Wait Time
- The elapsed time that the user task waited for redispatch on the
CICS QR mode TCB. This is an aggregate of the wait times between each
wait event completion and the user task being redispatched by the
CICS dispatcher domain on the QR mode TCB (field: QRMODDLY, owner:
DFHTASK, field ID 249).
- Resource Manager Interface (RMI) elapsed time
- The total elapsed time the user task spent in the CICS Resource Manager Interface (RMI) for all
the resource managers invoked by the user task, including DB2®, IMS™ (DBCTL), WebSphere® MQ, CICS Sockets, and so on (field: RMITIME, owner:
DFHTASK, field ID: 170).
- Resource Manager Interface (RMI) suspend time
- The elapsed time during which the user task was suspended by the CICS dispatcher domain whilst in
the CICS Resource Manager Interface
(RMI) (field: RMISUSP, owner: DFHTASK, field ID: 171).
Suspend Detail
This section details the
components of the Suspend Wait Time reported in the Summary
Data section.
The column headings in this part of the Wait Analysis
report are:
- Suspend Time
-
- Total
- Total component Suspend Time.
- Average
- Average component Suspend Wait Time, calculated as Total component
Suspend Time divided by #Tasks (from Summary Data).
- %age
- Percentage of time this component contributed to the Suspend Time,
calculated as Total component Suspend Time divided by Suspend Wait
Time (from Summary Data) multiplied by 100.
- Graph
- A histogram representation of the %age value with one asterisk
per 5%. 100% is 20 asterisks, 5% is one asterisk. Any value less than
5% does not appear in the graph.
- Count
-
- Total
- Total component suspend count.
- Average
- Average component suspend count, calculated as Total Count divided
by #Tasks (from Summary Data).
The Suspend Detail includes one report line
for every Suspend component clock with a non-zero value. The components
are reported in descending wait time order, ensuring that the primary
cause of task wait is at the top of the list.
Note that occasionally
there are Suspend Events that are wholly contained within another
Suspend Event. These events are shown with their Suspend Description
prefixed with >. For example, DSPDELAY contains TCLDELAY
and MXTDELAY. Dependent Suspend event metrics are not included in
Totals as their Parent event is assumed to contain all of the dependent
events' resource usage.
- N/A
- Occasionally, the total task suspend
time is greater than the sum of the component suspend times. This
unaccounted time is reported with a Field Name of N/A and a
description of Other Wait Time. This unaccounted time is calculated
as the difference between Suspend Wait Time (from the Summary Data
section) minus the sum of the component values (from the Suspend Detail
section). The Other Wait Time count value is calculated similarly.
- CFDTWAIT CF Data Table access requests wait time
- The elapsed time in which the user task waited for a data table
access request to the coupling facility data table server to complete
(owner: DFHFILE, field ID: 176).
- DB2CONWT DB2 Connection
wait time
- The value of this field depends on the version of DB2 to which CICS is
connected:
- When CICS is connected
to DB2 Version 5 or earlier,
and is therefore not exploiting the CICS open
transaction environment, (OTE) this field is the elapsed time in which
the user task waited for a CICS subtask
(TCB) to become available.
- When CICS is connected
to DB2 Version 6 or later, and
so is using the CICS open transaction
environment (OTE), this field is the elapsed time in which the user
task waited for a DB2 connection
to become available for use with the user tasks open TCB.
(owner: DFHDATA, field ID: 188)
- DB2RDYQW DB2 Thread wait
time
- The elapsed time in which the user task waited for a DB2 thread to become available (owner: DFHDATA,
field ID: 187).
- DSCHMDLY Redispatch wait time caused by change-TCB mode
- The elapsed time in which the user task waited for redispatch
after a CICS Dispatcher change-TCB
mode request was issued by or on behalf of the user task. For example,
a change-TCB mode request from a CICS L8
or S8 mode TCB back to the CICS QR
mode TCB might have to wait for the QR TCB because another task is
currently dispatched on the QR TCB (owner: DFHTASK, field ID: 247).
- DSMMSCWT CICS Dispatcher MVS™ Storage Constraint wait time
- The elapsed time which the user task spent waiting because no
TCB was available, and none could be created because of MVS storage constraints (owner: DFHTASK, field
ID: 279).
- DSPDELAY First Dispatch wait time
- The elapsed time in which the user task waited for the first dispatch
by the CICS dispatcher domain
(owner: DFHTASK, field ID: 125).
- DSTCBMWT CICS Dispatcher
TCB Mismatch wait time
- The elapsed time which the user task spent in TCB Mismatch waits,
that is, waiting because there was no TCB available matching the request,
but there was at least one non-matching free TCB (owner: DFHTASK,
field ID: 279). For transactions that invoke a Java™ program to run in a JVM, this shows the
time spent waiting for a TCB of the correct mode (J8 or J9) and JVM
profile.
- ENQDELAY Local Enqueue wait time
- The elapsed time in which the user task waited for a CICS task control local enqueue (owner: DFHTASK,
field ID: 129).
- FCIOWTT File I/O wait time
- The elapsed time in which the user task waited for non-RLS file
I/O (owner: DFHFILE, field ID: 063).
- GNQDELAY Global Enqueue wait time
- The elapsed time in which the user task waited for a CICS task control global enqueue (owner: DFHTASK,
field ID: 123).
- GVUPWAIT Give up control wait time
- The elapsed time in which the user task waited as a result of
giving up control to another task (owner: DFHTASK, field ID: 184).
- ICDELAY Interval Control (IC) wait time
- The elapsed time that the user task waited as a result of issuing
either:
- An interval control EXEC CICS DELAY
command for a specified time interval, or
- An interval control EXEC CICS DELAY
command for a specified time of day to expire, or
- An interval control EXEC CICS RETRIEVE
command with the WAIT option specified.
(owner: DFHTASK, field ID: 183).
- IMSWAIT IMS (DBCTL) wait
time
- The total elapsed time in which the user task waited for IMS (DBCTL) to service the IMS requests issued by the user task
(owner: DFHDATA, field ID: 186).
- IRIOWTT MRO link wait time
- The elapsed time in which the user task waited for control to
return at this end of an MRO (Inter-Region Communication) connection
(owner: DFHTERM, field ID: 100).
- ISIOWTT IPCONN link wait time
- The elapsed time for which a user task waited for control at this
end of an IPIC connection (owner: DFHSOCK, field ID: 300).
- JCIOWTT Journal I/O wait time
- The elapsed time in which the user task waited for journal (logstream)
I/O (owner: DFHJOUR, field ID: 010).
- JVMTHDWT JVM server thread wait time
- The elapsed time that the user task waited to obtain a JVM server
thread because the CICS system
had reached the thread limit for a JVM server in the CICS region (owner: DFHTASK, field ID: 401).
- LMDELAY Lock Manager (LM) wait time
- The elapsed time in which the user task waited to acquire a lock
on a resource. A user task cannot explicitly acquire a lock on a resource,
but many CICS modules lock
resources on behalf of user tasks using the CICS lock manager (LM) domain (owner: DFHTASK,
field ID: 128).
- LU61WTT LU6.1 wait time
- The elapsed time in which the user task waited for I/O on a LUTYPE6.1
connection or session. This time includes the waits for conversations
across LUTYPE6.1 connections, but not the waits incurred due to LUTYPE6.1
syncpoint flows. (owner: DFHTERM, field ID: 133).
- LU62WTT LU6.2 wait time
- The elapsed time in which the user task waited for I/O on a LUTYPE6.2
connection or session. This time includes the waits for conversations
across LUTYPE6.2 (APPC) connections, but not the waits incurred due
to LUTYPE6.2 (APPC) syncpoint flows (owner: DFHTERM, field ID: 134).
- MAXHTDLY Max Hot-Pooling TCB Delay time
- The elapsed time in which the user task waited to obtain a CICS Hot-Pooling TCB (H8 mode),
because the CICS system had
reached the limit set by the system parameter, MAXHPTCBS (owner: DFHTASK,
field ID: 278). The H8 mode open TCBs are used exclusively by HPJ-compiled Java programs defined with HOTPOOL(YES). This field is not available from CICS Transaction Server V3.1.
- MAXOTDLY MAXOPENTCBS wait time
- The elapsed time in which the user task waited to obtain a CICS open mode TCB because the CICS system had reached the limit
set by the system parameter, MAXOPENTCBS (owner: DFHTASK, field ID:
250).
- MAXSTDLY Maximum SSL TCB delay time
- The elapsed time in which the user task waited to obtain a CICS SSL TCB (S8 mode), because
the CICS system had reached
the limit set by the system initialization parameter MAXSSLTCBS. The
S8 mode open TCBs are used exclusively by secure sockets layer (SSL)
pthread requests issued by or on behalf of a user task (owner: DFHTASK,
field ID: 281).
- MAXTTDLY Maximum JVM server thread TCB delay time
- The elapsed time in which the user task waited to obtain a T8
TCB, because the CICS system
reached the limit of available threads. The T8 mode open TCBs are
used by a JVM server to perform multithreaded processing. Each T8
TCB runs under one thread. The thread limit is 2000 for
each CICS region and each JVM
server in a CICS region can
have up to 256 threads.
- MAXXTDLY Maximum XPLink TCB delay time
- The elapsed time in which the user task waited to obtain a CICS XP TCB (X8 or X9 mode), because
the CICS system had reached
the limit set by the system parameter, MAXXPTCBS. The X8 and X9 mode
open TCBs are used exclusively by C and C++ programs that were compiled
with the XPLINK option (owner: DFHTASK, field ID: 282).
- MXTDELAY First Dispatch MXT wait time
- The elapsed time in which the user task waited for first dispatch
which was delayed because of the limits set by the MXT system parameter
being reached (owner: DFHTASK, field ID: 127).
- PTPWAIT 3270 Bridge Partner wait time
- The elapsed time in which the user task waited for the 3270 bridge
partner transaction to complete (owner: DFHTASK, field ID: 285).
- RLSWAIT RLS File I/O wait time
- The elapsed time in which the user task waited for RLS file I/O
(owner: DFHFILE, field ID: 174).
- RQPWAIT Request Processor wait time
- The elapsed time during which the request processor user task
CIRP waited for any outstanding replies to be satisfied (owner: DFHTASK,
field ID: 193).
- RQRWAIT Request Receiver wait time
- The elapsed time during which the request receiver user task CIRR
(or user specified transaction ID) waited for any outstanding replies
to be satisfied (owner: DFHTASK, field ID: 192).
- RRMSWAIT Resource Recovery Services Indoubt wait time
- The elapsed time in which the user task waited indoubt using the MVS resource recovery services (RRS)
for transactional EXCI (owner: DFHTASK, field ID: 191).
- RUNTRWTT BTS run Process/Activity wait time
- The elapsed time in which the user task waited for completion
of a transaction that ran as a result of the user task issuing a CICS BTS run ACQPROCESS or run
activity request to run a process or activity synchronously (owner:
DFHTASK, field ID: 195).
- SOIOWTT Inbound Socket I/O wait time
- The elapsed time in which the user task waited for inbound socket
I/O (owner: DFHSOCK, field ID: 241).
- SOOIOWTT Outbound Socket I/O wait time
- The elapsed time in which the user task waited for outbound socket
I/O (owner: DFHSOCK, field ID: 299).
- SRVSYWTT CF Data Table syncpoint wait time
- The elapsed time in which the user task waited for completion
of syncpoint or resynchronization processing using the coupling facility
data table server to complete (owner: DFHSYNC, field ID: 177).
- SYNCDLY SYNCPOINT parent request wait time
- The elapsed time in which the user task waited for a syncpoint
request to be issued by it's parent transaction (owner: DFHSYNC, field
ID: 196). The user task was executing as a result of the parent transaction
issuing a CICS Business Transaction
Services (BTS) Run ACQPROCESS or Run Activity requests to run a process
or activity synchronously.
- SZWAIT FEPI services wait time
- The elapsed time in which the user task waited for FEPI services
(owner: DFHFEPI, field ID: 156).
- TCIOWTT Terminal wait for input time
- The elapsed time in which the user task waited for input from
the terminal user, after issuing an EXEC CICS RECEIVE request (owner: DFHTERM, field
ID: 009).
- TCLDELAY First Dispatch TCLSNAME wait time
- The elapsed time in which the user task waited for first dispatch
which was delayed because of the limits set for this transaction's
transaction class (owner: DFHTASK, field ID: 126).
- TDIOWTT VSAM transient data I/O wait time
- The elapsed time in which the user task waited for VSAM I/O to
the intrapartition transient data set, DFHINTRA (owner: DFHDEST, field
ID: 101).
- TSIOWTT VSAM TS I/O wait time
- The elapsed time in which the user task waited for VSAM I/O to
the auxiliary temporary storage data set, DFHTEMP (owner: DFHTEMP,
field ID: 011).
- TSSHWAIT Asynchronous Shared TS wait time
- The elapsed time in which the user task waited for an asynchronous
shared temporary storage request to a temporary storage data server
to complete (owner: DFHTEMP, field ID: 178).
- WMQGETWT WebSphere MQ
GETWAIT wait time
- The elapsed time the user task waited for WebSphere MQ to service the user task's
GETWAIT request (owner: DFHDATA, field ID: 396).
- WTCEWAIT CICS ECB wait
time
- The elapsed time the user task waited for:
- One or more ECBs, passed to CICS by
the user task using the EXEC CICS WAITCICS
ECBLIST command, to be MVS POSTed.
- Completion of an event initiated by the same or by another task.
(owner: DFHTASK, field ID: 182).
- WTEXWAIT External ECB wait time
- The elapsed time the user task waited for one or more ECBs, passed
to CICS by the user task using
the EXEC CICS WAIT EXTERNAL
ECBLIST() command, to be MVS POSTed.
(owner: DFHTASK, field ID: 181).