Start of change

MXTBYTOD: MXT exceeded - MAXTASKS Analysis by Time-of-Day

This report is a summary of the transactions that were delayed because the MXT limit was reached.

The report is summarized by time interval, MXT limit, and transaction ID. This information helps you identify the period to analyze to determine why the MXT limit was reached.

Tip: To see which CICSĀ® region MaxTasks relates to, add the APPLID field to form MXTBYTOD.

Most important columns: MaxTasks, #Tasks, Avg MXTDelay Time, and Avg Response Time.

Figure 1. MXTBYTOD report output
  V5R4M0                                                 CICS Performance Analyzer
                                                            Performance Summary
                                             __________________________________________________
 MXTBYTOD Printed at 14:05:40  2/01/2016     Data from 16:11:19  7/27/2015 to 16:11:43  7/27/2015
 MXT exceeded - MAXTASKS Analysis by Time-of-Day

                                          Avg      Max      Avg      Avg      Avg      Max      Avg      Max      Avg      Avg
 Stop     MaxTasks Tran       #Tasks Response Response Dispatch User CPU  Suspend  Suspend DispWait DispWait QRModDly MXTDelay
 Interval                                Time     Time     Time     Time     Time     Time     Time     Time     Time     Time
 16:11:00      500 EE1             8  15.8925  22.5661    .0010    .0007  15.8915  22.5654    .0507    .1078    .0503   1.5396
 16:11:00      500 HT1             3  10.5783  13.7109    .0016    .0013  10.5768  13.7103    .0640    .0956    .0634   1.2345
 16:11:00      500 JT1             2   6.6507   6.6534    .0006    .0004   6.6502   6.6529    .0253    .0283    .0245   1.9319
 16:11:00      500 JT2             4   5.1222   5.1233    .0017    .0014   5.1205   5.1217    .0712    .0802    .0709   1.9319
 16:11:00      500 JT8             4  19.0598  22.3857    .0043    .0016  19.0555  22.3840    .1065    .1329    .1013   1.6705
End of change