
MXTBYTSK: MXT exceeded - MAXTASKS Analysis by Task Time
This report identifies the transactions whose response times were higher because the MXT limit was reached.
MXTDelay Time is the time the transaction had to wait because the region had reached the MXT limit. The delay could be caused by a large number of tasks running at the same time or by an unexpectedly high response time of other transactions.
The report shows the transactions that were delayed, rather than the transactions that caused the delay. To investigate further, examine those transactions that were already running in the region at the time of the MXT delay.
Tip: To see which CICSĀ® region MaxTasks and CurTasks relate to, add the APPLID field to form MXTBYTSK.
Most important columns: MaxTasks, CurTasks, MXTDelay Time, and Response Time.
Figure 1. MXTBYTSK
report output
V5R4M0 CICS Performance Analyzer
Performance List
__________________________________________________
MXTBYTSK Printed at 14:05:40 2/01/2016 Data from 16:11:25 7/27/2015 APPLID IYCYZC20
MXT exceeded - MAXTASKS Analysis by Task Time
Stop MaxTasks CurTasks Tran TaskNo Response Dispatch User CPU KY8 CPU KY9 CPU Suspend DispWait QRModDly MXTDelay
Time Time Time Time Time Time Time Time Time Time
16:11:25.470 500 389 JT2 1685 5.1210 .0015 .0014 .0000 .0000 5.1194 .0665 .0665 1.9323
16:11:25.470 500 389 JT2 1668 5.1219 .0017 .0015 .0000 .0000 5.1202 .0697 .0693 1.9315
16:11:25.471 500 390 JT2 1695 5.1226 .0019 .0014 .0000 .0000 5.1207 .0685 .0681 1.9327
16:11:25.472 500 281 JT2 1658 5.1233 .0016 .0014 .0000 .0000 5.1217 .0802 .0796 1.9310
