
WAIT0001: MXT exceeded
The Wait Analysis Report provides a breakdown of wait activity by Transaction ID. You can quickly see why transactions are being suspended.
You use this report to determine if transactions experienced waits that caused delays in response time, which might have caused the region to reach the MXT limit as a consequence.
Most important columns: # Tasks, Time Average, and Ratio.
Figure 1. WAIT001
report output
V5R4M0 CICS Performance Analyzer
Wait Analysis Report
__________________________________________________
WAIT0001 Printed at 14:05:40 2/01/2016 Data from 16:11:18 7/27/2015 to 16:24:04 7/27/2015
MXT exceeded
-------------------------------------------------------------------------------------------------------------------------------
Tran=HT2
Summary Data -------- Time --------- ------ Count ------ ------ Ratio ------
Total Average Total Average
# Tasks 746
Response Time 962.4299 1.2901
Dispatch Time 0.5147 0.0007 6958 9.3 0.1% of Response
CPU Time 0.4287 0.0006 6958 9.3 83.3% of Dispatch
Suspend Wait Time 961.9152 1.2894 6958 9.3 99.9% of Response
Dispatch Wait Time 12.4397 0.0167 6212 8.3 1.3% of Suspend
QR TCB Redispatch Wait Time 12.1550 0.0163 3895 5.2 97.7% of Dispwait
Resource Manager Interface (RMI) elapsed time 0.0202 0.0000 4476 6.0 0.0% of Response
Resource Manager Interface (RMI) suspend time 0.0105 0.0000 74 0.1 0.0% of Suspend
Suspend Detail ------------------- Suspend Time ------------------- ----- Count -----
Total Average %age Graph Total Average
JCIOWTT Journal I/O wait time 644.8995 0.8645 67.0% |************* 895 1.2
LMDELAY Lock Manager (LM) wait time 311.7012 0.4178 32.4% |****** 227 0.3
N/A Other Wait Time 2.1043 0.0028 0.2% | 7 0.0
FCXCWTT VSAM exclusive control wait time 1.6470 0.0022 0.2% | 2 0.0
DSCHMDLY Redispatch wait time caused by change-TCB mode 0.7497 0.0010 0.1% | 4486 6.0
FCIOWTT File I/O wait time 0.4062 0.0005 0.0% | 587 0.8
DSPDELAY First dispatch wait time 0.4044 0.0005 0.0% | 746 1.0
ENQDELAY Local Enqueue wait time 0.0029 0.0000 0.0% | 8 0.0
