gtps3m0mSystem Performance and Measurement Reference

Message Data Analysis

Message Summary Report

Message Summary reports are produced according to your options (see Figure 54). The system-wide message summary report presents basic local network line statistics calculated from captured TPF counters. The application-based message summary report presents local network line statistics for each specified application, calculated from intercepted input/output messages. This report is related only to the high-speed local network lines including SDLC cross-domain links, and BSC/SLC links (except for SDLC and ALC lines of cross-domain resources which are reported if the associated NCP is shared by other CPUs).

The systemwide message summary is the first part of the Message Summary Report. Each pseudo line is reported by the actual line, that is, by the name given to the physical line. For the Network Extension Facility (NEF), the SNA node name given to each ALC line is used instead of the pseudo ALC lines. The Message Summary by Line Report may not be meaningful for a NEF network. The application based message summary does not report message-routing traffic to and from SDLC cross-domain links, except for application-to-application messages which are reported in the CPU section of the Message Summary Report. Messages of cross-domain sessions -- those between applications of the TPF system and the cross-domain resources (including primary and secondary applications LUs) -- are reported in the associated cross-domain link section. Because NEF resources are considered cross-domain resources, NEF messages are reported in the cross-domain link section.

The message rates are calculated from messages recorded during the message collector interval. Comparing these values to those reported in the System Summary Report should provide close correlation for the means.

The high-speed output message queue refers to a snapshot sample of the total number of messages which are in queue for output to the 2703, (3705EP), and 3705 NCP lines.

Inordinately high line queues are indications of line problems or overloading and should be investigated further. Line loading or utilization can be readily calculated by using 400 and 800 characters per record to represent 100% utilization of a 2400 and 4800 baud line, respectively.

Figure 54. Message Summary Report


MESSAGE SUMMARY                                           SYSTEM WIDE
LINE NO/                   INPUT    MEAN INPUT      INPUT       OUTPUT MSGS
NODENAME      TYPE       MSGS/SEC   MSG LENGTH    CHARS/SEC     /INPUT MSGS
 
    3E        BYSC PP        0.00         0.00        0.00           0.00
    3F        BYSC PP        0.00         0.00        0.00           0.00
    40        BYSC PP        0.00         0.00        0.00           0.00
    41        BYSC MP        0.00         0.00        0.00           0.00
              STB1           0.00         0.00        0.00           0.00
              STB3           0.00         0.00        0.00           0.00
              ASSS           0.00         0.00        0.00           0.00
              BIRD           0.00         0.00        0.00           0.00
              COWS           0.00         0.00        0.00           0.00
              CROW           0.00         0.00        0.00           0.00
              DOGS           0.00         0.00        0.00           0.00
              EELS           0.00         0.00        0.00           0.00
              FAWN           0.00         0.00        0.00           0.00
              GOAT           0.00         0.00        0.00           0.00
              LAMB           0.00         0.00        0.00           0.00
              OWLS           0.00         0.00        0.00           0.00
              SEAL           0.00         0.00        0.00           0.00
    42        BYSC MP        0.00         0.00        0.00           0.00
              STB4           0.00         0.00        0.00           0.00
  
·
·
·
49 BYSC PP 0.00 0.00 0.00 0.00 4A BYSC MP 0.00 0.00 0.00 0.00 STD5 0.00 0.00 0.00 0.00 STB2 0.00 0.00 0.00 0.00 ASSS 0.00 0.00 0.00 0.00 BIRD 0.00 0.00 0.00 0.00 COWS 0.00 0.00 0.00 0.00 CROW 0.00 0.00 0.00 0.00 DOGS 0.00 0.00 0.00 0.00 EELS 0.00 0.00 0.00 0.00 FAWN 0.00 0.00 0.00 0.00 GOAT 0.00 0.00 0.00 0.00 LAMB 0.00 0.00 0.00 0.00 OWLS 0.00 0.00 0.00 0.00 SEAL 0.00 0.00 0.00 0.00 4B BYSC PP 0.00 0.00 0.00 0.00 4C BYSC PP 0.00 0.00 0.00 0.00 4D BYSC PP 0.00 0.00 0.00 0.00 LINK 1 0.00 0.00 0.00 0.00 34 AI 0.00 0.00 0.00 0.00 LINK 2 0.00 0.00 0.00 0.00 35 AI 0.00 0.00 0.00 0.00 36 AI 0.00 0.00 0.00 0.00 37 AI 0.00 0.00 0.00 0.00 38 AI 0.00 0.00 0.00 0.00 LINK 3 0.00 0.00 0.00 0.00 39 AI 0.00 0.00 0.00 0.00 3A AI 0.00 0.00 0.00 0.00 3B AI 0.00 0.00 0.00 0.00 3C AI 0.00 0.00 0.00 0.00

 

Action Code Summary Reports

System and File Summaries include only the number of messages on a per second basis. To establish a base from which data collection comparisons can be made, the number of input messages must be related to a message mix: that is, messages grouped by user defined transaction category.

When the message collector is run in continuous mode, the mean output lengths and mean existence time of each action group is also available. The existence time is from the time a message is placed on the input list until the SEND macro is issued. The sample reports represent the total system. The Action Code Summary (see Figure 55) may also be selected by line, city, or particular terminal interchange. Because NEF terminal addresses (LEIDs have no relationship to lines, cities, or terminal interchanges), the Action Code Summary Report based on line, city, or terminal interchange is not meaningful.

Figure 55. Action Code Summary Report


ACTION CODE SUMMARY

 
AAAA                                TOTAL INPUT           % OF     MSGS/     MEA
ACTION GROUP                          MESSAGES            TOTAL    SEC        LE
 
      AM                                  45              100.00   0.06        2
 
                        TOTALS            45              100.00   0.06        2
 
 
UNMATCHED OUTPUT                           1
% OF LINE'S TOTAL OUTPUT                 2.50
MEAN OUTPUT LENGTH                      24.00
 
 
'MEAN OUTPUT LENGTH' REFERS TO OUTPUT MESSAGES AS SEEN BY THE AGENT  (MAY BE COM
 

Application Summary and Detail Reports

Two reports related to applications are produced when the TPF system is generated with the Message Routing Facility. The Application Summary report is included in the System Summary (see Figure 5) section and is always produced. The Application Detail Report, when selected in the option cards, is produced to provide additional information (see Figure 56).

The Application Summary Report is used to analyze messages from the cross-domain network (whether they are through cross-domain SLU-PLU session or via Message Routing facility) to applications in the TPF system, and messages from local-domain resources to applications in other CPUs (through the message routing facility). The Application Detail Report breaks down, by each application in the network, the number of input messages for each application, the percentage of the total number for the system, the number of messages per second, and the mean input message length. The Application Detail report is printed only if the message routing facility is system-generated and message collection was active. If message collection was done in continuous mode, this report provides mean existence time for each application. In addition to local-domain messages, this report reflects cross-domain session input messages. System application (SA) records are used as input to this report.

Figure 56. Application Detail Report


 APPLICATION DETAIL REPORT                                 SYSTEM WIDE       10


 
                                     TOTAL INPUT          % OF      MSGS/    MEA
 APPLICATION                           MESSAGES           TOTAL     SEC       LE
 AAAA
 BALU
 BBBB
 B32O
 CCCC
 CISB
 CLGA
 CLGB
 CLGC
 CLGD
 CXFT
 CXJA
 CXJB
 DDDD
 ECHO
 EEEE
 EEE1
 FC14
 FFFF
 FFF1
 GAMB
 GGGG
 GGG1
 GMC1
 GMC2                                      27             12.75         0.17
 GMC3                                      15              7.12         0.09
 GMT1                                      14              6.62         0.08
 GMT2
 GMT3
 GMT4                                      13              6.12         0.08
 GMT5
 GMT6
 GMT7
 GMT8
 GMZ1                                      61             29.00         0.39
 GMZ2                                      80             38.00         0.51
 GMZ3
 GMZ4
 HHHH
 HHH1

·
·
·
VVVV WWWW XXXX YYYY ZZZZ 32NA 32NB 32NC 32ND TOTALS 210 100.00 1.34

City Summary Report

The City Summary Report (see Figure 57) lists input and output messages by cities served by the reservations network. Activity on remote terminals that are served by local line drops off a terminal interchange is reported as part of the traffic originating from the city code assigned to the terminal interchange. This report is also broken down by optioned application. This report includes messages of pseudo 3270 terminals and terminals of the Network Extension Facility (NEF) in the cross-domain network.

Figure 57. City Summary Report


CITY SUMMARY                         SYSTEM WIDE    03 APR   10:36:26    MESSAGE


 
                      INPUT MESSAGES                              OUTPUT MESSAGE
 
           MSG    % OF     MSGS/       MEAN INP       MSG      % OF      MSGS/
CITY      COUNT   TOTAL      SEC        LENGTH       COUNT     TOTAL       SEC
LAX          9    100.00   0.06         7.000           9      100.00    0.06
SLC
STL
DEN
ORD
PHX
COS
 
APPLICATION RES0
 
                    INPUT MESSAGES                                 OUTPUT MESSAG
 
           MSG    % OF     MSGS/       MEAN INP       MSG      % OF      MSGS/
CITY      COUNT   TOTAL      SEC        LENGTH       COUNT     TOTAL       SEC
 
LAX        125    26.65     0.06        15.00         210      35.59     0.10
COS
DEN        227    48.40     0.11        11.18         227      38.47     0.11
ABO
ORD
PHX
MKC
EIP
SLC
STL
TUS

Terminal Activity Report

The Terminal Activity Report (see Figure 58) is optioned by city and application. Individual terminal activity for all terminals associated with a city code is grouped in a convenient one-page report. The total counts of input and output messages by LNIA are also shown. At the bottom of the page the totals of message counts for the city are listed along with the percentages of the total system traffic that the counts represent. This report includes terminals of the Network Extension Facility (NEF) in the cross-domain network. Note that pseudo 3270 terminals are reported in the Logical Unit (LU) Activity Report. The Terminal Activity Report optioned by city is not meaningful for NEF terminal networks.

Figure 58. Terminal Activity Report


TERMINAL ACTIVITY     TPF/DSD Development     22 May 13:21:39    MESSAGE


HOU
 
       LNIA   0402    LNIA    0503     LNIA     0906     LNIA    0B01
 
TA     INP     OUT    INP      OUT     INP       OUT      INP     OUT
 
02                      6        1
10       2       1      3        3       4         3
11       4       3      9       10
12       1       1                       1         1
13      11      11      1        1                          4       4
14                                       1         1        6       6
15
16       9      10     10       10                          3       3
17      16      15      6        6       1         1
18       2       2      3        4
19       3       3                       1         1
1A      10       9      1        1       3                  6       7
1B                                                          1       1
20       2       2                                          3       3
22                      4        4
23       6       7
25       8       9
26                      1        1
28       5       5                                          14      14
2A                                                           7       7
 
TOTAL   79      78     44       41      12         8        44      45
 
TOTAL INP MESSAGES  =      179
PERCENT OF TOTAL INP=  8.16
 
TOTAL OUTP MESSAGES =      172
PERCENT OF TOTAL OUT=  7.65
 
TERMINAL ACTIVITY   TPF Development     18 Oct   14:16:02   MESSAGE
LAX
RES0
        LNIA 0201    LNIA 0202    LNIA 0203    LNIA 0204   LNIA 0205   LNIA 0206
 
TA      INP   OUT    INP   OUT    INP   OUT     INP  OUT   INP   OUT   INP   OUT
 
TOTAL      ALL VALUES ARE ZERO
 
 
TERMINAL ACTIVITY   TPF Development     18 Oct  14:16:02    MESSAGE
 
    (CONT'D)
        LNIA 0301    LNIA 0302    LNIA 0303    LNIA 0304   LNIA 0305   LNIA 0306
 
TA      INP   OUT    INP   OUT    INP    OUT   INP   OUT   INP   OUT   INP   OUT
 
02                     1
05
06       13    20
 
TOTAL    13    20      1
 
TERMINAL ACTIVITY   TPF Development     18 Oct 14:16:02 MESSAGE
 
     (CONT'D)
        LNIA 0309    LNIA 030B    LNIA 0701    LNIA 0708    LNIA 0709  LNIA 0804
 
TA      INP   OUT    INP   OUT    INP   OUT    INP   OUT     INP  OUT  INP   OUT
 
TOTAL     ALL VALUES ARE ZERO
 
TERMINAL ACTIVITY   TPF Development      18 Oct 14   :16:02   MESSAGE
 
      (CONT'D)
        LNIA 0C01    LNIA 0C02    LNIA 0C03    LNIA 0C04    LNIA 1804
 
TA      INP   OUT    INP   OUT    INP   OUT    INP   OUT    INP   OUT
 
TOTAL      ALL VALUES ARE ZERO
 
TOTAL INP MESSAGES  =       125
% OF INP OF THIS CITY  81.16
PERCENT OF TOTAL INP=  26.65
 
TOTAL OUTP MESSAGES =       210
% OF OUT OF THIS CITY  87.86
PERCENT OF TOTAL OUT=  35.59
 
 

Logical Unit Activity Report

The Logical Unit (LU) Activity Report is optioned by SNA line name (node name) and application (see Figure 59). The individual activity for all logical units associated with a line is grouped by cluster controller and its related logical units on this report. The total counts of input and output messages by cluster are also shown. At the bottom of the page the totals of message counts for the line are listed along with the percentages of the total system-wide SNA traffic that the counts represent. Pseudo 3270 terminals are included in this report. To obtain activities of cross-domain logical units, specify the proper cross-domain link in the option cards.

Figure 59. Logical Unit Activity Report


LU ACTIVITY    TPF Development       03 APR   12:16:32    MESSAGE




 
WILDCARD SPECIFIED: LN2C*
 
LU NAME   INP  OUT LU NAME   INP  OUT LU NAME   INP   OUT LU NAME  INP   OUT LU
 
LN2C1411   0    0 LN2C1412    0    0 LN2C1413   37   31 LN2C1414    0    0 LN2C1
 
LN2C1417   0    0 LN2C1418    0    0 LN2C1421    0    0 LN2C1422    0    0 LN2C1
 
LN2C1425  40   60 LN2C1426    0    0 LN2C1427    0    0 LN2C1428    0    0 LN2C1
 
LN2C1433   0    0 LN2C1434    0    0 LN2C1435    0    0 LN2C1436    0    0 LN2C1
 
LN2C1440   0    0 LN2C1441   62   48 LN2C1442    0    0 LN2C1443    0    0 LN2C1
 
LN2C1446   0    0 LN2C1447    0    0 LN2C1448    0    0 LN2C1450    0    0 LN2C1
 
LN2C1453   0    0 LN2C1454    0    0 LN2C1455    0    0 LN2C1456    0    0 LN2C1
 
LN2C1460   0    0 LN2C1461    0    0 LN2C1462    0    0 LN2C1463    0    0 LN2C1
 
LN2C1466   0    0 LN2C1467    0    0 LN2C1468    0    0
 
 
TOTAL INP MESSAGES  =   139
TOTAL OUTP MESSAGES =   139
 
 

Logical Unit Message Stream Report

This report is optioned by SNA line name (node name) (see Figure 60). Only one line is permitted for each run against the reduction. If both the SNA line and city Message Stream reports are optioned, only one will be generated while the other is ignored. The normal report will print the total text of the input messages and as many as 65 characters of the output messages unless the suboption to print the entire output message has been chosen. The report is arranged by nodename so that all messages from a specific LU are listed in sequence before beginning the printout of messages from the next LU. This report, when optioned by city, may not be meaningful for NEF terminal networks.

To obtain the message stream of pseudo 3270 terminals, a SNA line node name must be chosen.

The TOD clock is listed for each message so that the time between successive message entries from an LU can be analyzed. The existence time approximates the length of time required to process the message in the CPU. The existence time is not printed for some messages when collection is made in sampling mode because input or output messages may not be available at the beginning and end of intervals. This section explains the variables that are affected by the online system environment and by the collectors' data recording methods, and offline by the unique constants of the reduction programs, assumptions, and data manipulation techniques. The aim of this section is to provide those details of collection and reduction that may not be readily apparent to the user, but are necessary for a serious analysis of one's system based on the System Performance reports. The I-stream number will be reported for output messages.

Note:
A logical unit (LU) resource is included in the LU Message Stream Report only if a resource vector table (RVT) entry exists for that LU resource when data collection is started. If an RVT entry is created for an LU resource after data collection is started, that LU resource is not included in this report.

Figure 60. Message Stream Report by LU


MESSAGE STREAM BY LU        TPF Development       19 Oct   02:38:16


 
NODENAME     MESSAGE TYPE      MESSAGE TEXT
LN2C1445
 
SESSION 1    CONVERSATION 1
 
             OUTPUT            01 ALL PROCESSED ....... ............... ........
                               ......... .............. ............... ........
                               ......... .............. ............... ........
                               ......... .............. ............... ........
                               ......... .............. ............... ........
                               ......... .
 
             INPUT             J/1/A
             OUTPUT            01 ALL PROCESSED ....... ............... ........
                               ......... ......END + %
 
             INPUT             J/1A i
             OUTPUT            01 ALL PROCESSED ....... ...............
                               ......... .............. .........END
 
             INPUT             J/1/A
             OUTPUT            01 All PROCESSED .......END
 
             INPUT             J/1C %
             OUTPUT            01 ALL PROCESSED ....... ............... ........
                               ......... .............. ............... ........
                               ......... .............. ............... ........
                               ......... .............. ............... ........
                               ......... .............. ............... ........
                               ......... .
 
             INPUT             J/1C
             OUTPUT            01 ALL PROCESSED ....... ............... ........
                               ......... .............. ............... ........
 
 
 

Message Stream Report

This report can be optioned by city (see Figure 61). If both the SNA line and city Message Stream reports are optioned, only one will be produced while the other will be ignored. Only one city is permitted for each run against the reduction program. The normal report will print the total text of the input messages and as many as 65 characters of the output messages. A suboption does permit printing the entire output message. The report is arranged by LNIATA/LEID so that all messages from a particular terminal are listed in sequence before starting the printout of messages from the next terminal. This report, when optioned by city, may not be meaningful for NEF terminal networks.

The time-of-day (TOD) clock is listed for each message so that the time between successive message entries from a terminal can be analyzed. The Existence Time approximates the length of time required to process the message in the CPU. Existence time will not be printed for some messages when collection was made in sampling mode because input or output messages may not be available at the beginning and end of intervals. The I-stream number of the output message will also be reported.

Note:
A logical unit (LU) resource is included in the Message Stream Report only if a resource vector table (RVT) entry exists for that LU resource when data collection is started. If an RVT entry is created for an LU resource after data collection is started, that LU resource is not included in this report.

Figure 61. Message Stream Report by Agent


MESSAGE STREAM BY AGENT     TPF Development                              MESSAGE


 
ABQ
LN IA TA     MESSAGE TYPE         MESSAGE TEXT                               TIM
06 02 10                                                                     SIN
 
             INPUT                *R                       +                   2
             OUTPUT               /$ 1. 1PPAAAAAA
                                   1 CO 165Y 23OCT ABQELP SS1  327P  413P
                                  FONE-ABQABQ0000406
                                  TLT-TL0
                                  HA FAX-OSI HAFAX
                                  GEN FAX-OSI FAX
                                  >+
 
             INPUT                0A
 
                                                 +
             OUPUT                /F 2 ARNK
                                  >+
 
             INPUT                0166Y19NOVDENMKCNN1             +
             OUTPUT               /G 3   166Y 19NOV DENMKC SS1 83OP 952P
                                  >+
 
             INPUT                0169Y19DECMKCDENNN1     +
             OUTPUT               /
                                  RPT ENT
                                  >+
 
             INPUT                0A                      +
             OUTPUT               /H 4 ARNK
                                  >+
 
             INPUT                0173Y18JANDALABQNN1     +
             OUTPUT               /
                                  INVLD DATE
                                  >+
 
             INPUT                0174Y17FEBABQDALNN1     +
             OUTPUT               /
                                  INVLD DATE
                                  >+
 
             INPUT                *1                     +
             OUTPUT               /$ 1 CO 165Y 23OCT ABQELP SS1 327P 413
                                  2   ARNK
                                  3 CO 166Y 19NOV DENMKC SS1 830P 952P
                                  4   ARNK
                                  >+
 

Distributed Data Management (DDM) Message Stream Report

This report is printed if the SNA STREAM DDM option is requested (see Figure 62). One report is printed for each SLU (that is, node) found to be sending or receiving DDM message traffic. The output DDM messages and the input DDM messages are listed in chronological order. The remote response time is calculated for any input message that immediately follows an output message. It should be noted that DDM messages are paired as output/input message pairs and that there may be multiple responses (input messages) to a single request (output message).

See TPF Application Requester User's Guide for more information about interpreting the data collection report for the TPF Application Requester (TPFAR) feature.

Note:
A logical unit (LU) resource is included in the DDM Message Stream Report only if a resource vector table (RVT) entry exists for that LU resource when data collection is started. If an RVT entry is created for an LU resource after data collection is started, that LU resource is not included in this report.

Figure 62. Distributed Data Management (DDM) Message Stream Report


DDM MESSAGE STREAM REPORT                                 SYSTEM WIDE



 
NODENAME     MESSAGE TYPE       MESSAGE TEXT
 
CTCCC003
 
SESSION 1    CONVERSATION 1
             OUTPUT             0048D041 00000042 10410014 14041403 00031444
                                00032407 0003240F 00030004 115D0008 1147D8E3
                                D7C60015 116D40C4 C1D5C2E4 D9E8E3D7 C6D5C5E3
                                4040C300 09115AE3 D7C6F3F1 0049D001 00010043
                                20010016 2110C4C2 F2F3E3E2 E3404040 40404040
                                40404040 0006210F 2407000D 002FD8E3 C4E2D8D3
                                F3F7F000 0A003500 06119C01 F4000C11 2EE3D7C6
                                F0F3F0F1 F0
 
             INPUT              0056D043 00000050 14430010 115EC4C2 C1C1F0F2
                                F7C3F5F5 C4F80014 14041403 00031444 00032407
                                0003240F 00030008 1147D8C4 C2F20014 116DC4C2
                                F2F3E3E2 E3404040 40404040 4040000C 115AC4E2
                                D5F0F2F0 F3F0004C D0020001 00462201 00061149
                                0000000D 002FD8E3 C4E2D8D3 F3F7F000 0C112EC4
                                E2D5F0F2 F0F3F000 0A003500 06119C01 F4001921
                                35E3D7C6 D5C5E34B C3E3C3C3 C3F0F0F3 A3F87E4A
                                5554
 
 
             OUTPUT             0069D051 00020063 200B0016 2110C4C2 F2F3E3E2
                                E3404040 40404040 40404040 00442113 C4C2F2F3
                                E3E2E340 40404040 40404040 4040E3D7 C6D5C5E3
                                6DC2E2E2 6DC8D7D5 40404040 D8E7D5F0 40404040
                                40404040 40404040 40401477 8BE210BD 10100001
                                00052111 F00013D0 53000200 0D002FD8 E3C4E2D8
                                D3F3F7F0 0010D003 0002000A 00350006 119C01F4
 
             INPUT              000BD003 00020005 2408FF
 
 
             OUTPUT             0069D051 00030063 200B0016 2110C4C2 F2F3E3E2
                                E3404040 40404040 40404040 00442113 C4C2F2F3
                                E3E2E340 40404040 40404040 4040E3D7 C6D5C5E3
                                6DC2E2E2 6DC8D7D5 40404040 D8E7D5F0 40404040
                                40404040 40404040 40401477 8BE210BD 10100002
                                00052111 F00013D0 53000300 0D002FD8 E3C4E2D8
                                D3F3F7F0 0010D003 0003000A 00350006 119C01F4
 
             INPUT              000BD003 00030005 2408FF
 

TCP/IP Message Summary Report

This report includes information about the number of messages, bytes, and packets that are sent and received by each TCP/IP native stack application. The TCP/IP message summary report includes the following information:

The information in this report is shown in descending order by input messages per second; that is, the application with the highest number of input messages per second is shown at the top.

The following shows an example of a TCP/IP message summary report.

Figure 63. TCP/IP Message Summary Report


TCP/IP MESSAGE SUMMARY                                                           04 FEB        14:44:57     MESSAGE    PAGE     1
 
APPLICATION    PORT  WEIGHT                             INPUT                                            OUTPUT
                                    MSGS/SEC         PKTS/SEC       BYTES/SEC         MSGS/SEC         PKTS/SEC       BYTES/SEC
 
TEST-9981      9981     ***           149.60           149.60          149598           149.60           149.60          149598
TEST-9980      9980     ***           149.49           149.49          149492           149.49           149.49          149492
TEST-9984      9984     ***           149.45           149.45          149451           149.45           149.45          149451
TEST-9982      9982     ***           149.44           149.44          149436           149.44           149.44          149436
TEST-9983      9983     ***           139.69           139.69          139686           139.69           139.69          139686
TEST-9985      9985     ***           139.66           139.66          139658           139.66           139.66          139658
OTHER                   ***             0.09             0.09              39             0.11             0.11               0
RIP             520      50             0.07             0.07               4             0.07             0.07               1
FTP-DATA         20     100             0.04             8.76           11883             0.00             1.39               0
TFTP             69     100             0.02             0.02               0             0.00             0.00               0
 
TOTAL                                 877.55           886.28          889251           877.50           878.89          877326

TPF MQSeries Data Collection Reports

MQSeries data collection provides data to effectively manage the performance of both channels and queues.

The TPF system collects data for each channel defined in MQSeries, including both sender and receiver channels. The channel data consists of the number of messages and the number of bytes being processed by each channel. This is for data arriving at the TPF system and for data being sent by the TPF system to remote MQSeries servers. The report provides mean message and data rates as well as the maximum message and data rates. See Figure 64 for an example of the TPF MQSeries message channel report.

The TPF system also collects data showing activity for the queue of each type defined. The report includes the following information:

Note:
The number of times the queue is opened and closed is not shown for transmission queues.

See Figure 65 for an example of the TPF MQSeries message queue report.

Figure 64. TPF MQSeries Message Channel Report


T P F   M*Q*S E R I E S   M E S S A G E - C H A N N E L   R E P O R T            04 MAR        14:29:43     MESSAGE    PAGE     1
 
BSS   SUBSYSTEM
 
================
MESSAGE CHANNELS FOR LOCAL QUEUE MANAGER:  TPFQM                                           ,   5 OBSERVATIONS,    24 SECONDS, CPU B
================
                                   MESSAGE RATE          TOTAL DATA RATE (BYTES)   INCOMING DATA RATE        OUTGOING DATA RATE
MESSAGE CHANNEL NAME   TYPE        MEAN      MAXIMUM     MEAN        MAXIMUM       MEAN        MAXIMUM       MEAN        MAXIMUM
--------------------   --------    --------- ---------   ----------- -----------   ----------- -----------   ----------- -----------
 
CHL1                   SERVER           3.72     18.61       3833.13    19164.87       2007.68    10038.02       1825.44     9126.85
CHL3                   SENDER           2.24     10.80       1198.93     5771.55         20.17       89.62       1178.76     5681.94
 
MESSAGE CHANNEL  T O T A L S            5.96 *********       5032.05 ***********       2027.85 ***********       3004.20 ***********
 
T P F   M*Q*S E R I E S   M E S S A G E - C H A N N E L   R E P O R T            04 MAR        14:29:43     MESSAGE    PAGE     2
 
BSS   SUBSYSTEM
 
================
MESSAGE CHANNELS FOR LOCAL QUEUE MANAGER:  TPFQM                                           ,   5 OBSERVATIONS,    24 SECONDS, CPU B
================
                                     NEGOTIATED          BATCH SIZE
MESSAGE CHANNEL NAME   TYPE          BATCH SIZE          MEAN        MAXIMUM
--------------------   --------      ----------          ----------  -----------
 
CHL3                   SENDER                10                1.50            5
 
MESSAGE CHANNEL  T O T A L S         **********                1.50  ***********
 
T P F   M*Q*S E R I E S   M E S S A G E - C H A N N E L   R E P O R T            04 MAR        14:29:43     MESSAGE    PAGE     3
 
BSS   SUBSYSTEM
 
================
MESSAGE CHANNELS FOR LOCAL QUEUE MANAGER:  TPFQM                                           ,   5 OBSERVATIONS,    24 SECONDS, CPU B
================
                                     MEAN ACTIVE         HIGH WATER MARK
MESSAGE CHANNEL NAME   TYPE          INSTANCES           INSTANCES
--------------------   --------      -----------         ---------------
 
CHL1                   SERVER               0.25                       2
 
MESSAGE CHANNEL  T O T A L S                0.25             ***********

Figure 65. TPF MQSeries Message Queue Report


T P F   M*Q*S E R I E S   M E S S A G E - Q U E U E   R E P O R T                04 MAR        14:29:43     MESSAGE    PAGE     1
 
BSS   SUBSYSTEM
 
==============
MESSAGE QUEUES FOR LOCAL QUEUE MANAGER:  TPFQM                                           ,   5 OBSERVATIONS,    24 SECONDS, CPU B
==============
 
MESSAGE QUEUE NAME:  DEAD.LETTER.QUEUE                               , MESSAGE QUEUE TYPE:  LOCAL
 
                        OPEN QUEUE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED OPENS PER SECOND
                       CLOSE QUEUE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED CLOSES PER SECOND
            ADD PERSISTENT MESSAGE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED PERSISTENT MESSAGES ADDED PER SECOND
         ADD NONPERSISTENT MESSAGE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED NONPERSISTENT MESSAGES ADDED PER SECOND
 
        ADDED PERSISTENT MESSAGE LENGTH:          0.00 MEAN,         0.00 MAXIMUM OBSERVED BYTES PER ADDED PERSISTENT MESSAGE
     ADDED NONPERSISTENT MESSAGE LENGTH:          0.00 MEAN,         0.00 MAXIMUM OBSERVED BYTES PER ADDED NONPERSISTENT MESSAGE
 
                            SWEEP COUNT:                                0 TOTAL OBSERVED SWEEPS DURING DATA COLLECTION RUN
 
....................................................................................................................................
 
MESSAGE QUEUE NAME:  Q1                                              , MESSAGE QUEUE TYPE:  LOCAL
 
                        OPEN QUEUE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED OPENS PER SECOND
                       CLOSE QUEUE RATE:          0.04 MEAN,         0.20 MAXIMUM OBSERVED CLOSES PER SECOND
            ADD PERSISTENT MESSAGE RATE:          3.00 MEAN,        15.01 MAXIMUM OBSERVED PERSISTENT MESSAGES ADDED PER SECOND
         ADD NONPERSISTENT MESSAGE RATE:          0.64 MEAN,         3.20 MAXIMUM OBSERVED NONPERSISTENT MESSAGES ADDED PER SECOND
 
        ADDED PERSISTENT MESSAGE LENGTH:         50.00 MEAN,        50.00 MAXIMUM OBSERVED BYTES PER ADDED PERSISTENT MESSAGE
     ADDED NONPERSISTENT MESSAGE LENGTH:         50.00 MEAN,        50.00 MAXIMUM OBSERVED BYTES PER ADDED NONPERSISTENT MESSAGE
 
                            SWEEP COUNT:                                5 TOTAL OBSERVED SWEEPS DURING DATA COLLECTION RUN
 
....................................................................................................................................
 
MESSAGE QUEUE NAME:  SPECIAL.RECOVERY.QUEUE                          , MESSAGE QUEUE TYPE:  LOCAL
 
                        OPEN QUEUE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED OPENS PER SECOND
                       CLOSE QUEUE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED CLOSES PER SECOND
            ADD PERSISTENT MESSAGE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED PERSISTENT MESSAGES ADDED PER SECOND
         ADD NONPERSISTENT MESSAGE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED NONPERSISTENT MESSAGES ADDED PER SECOND
 
        ADDED PERSISTENT MESSAGE LENGTH:          0.00 MEAN,         0.00 MAXIMUM OBSERVED BYTES PER ADDED PERSISTENT MESSAGE
     ADDED NONPERSISTENT MESSAGE LENGTH:          0.00 MEAN,         0.00 MAXIMUM OBSERVED BYTES PER ADDED NONPERSISTENT MESSAGE
 
                            SWEEP COUNT:                                0 TOTAL OBSERVED SWEEPS DURING DATA COLLECTION RUN
 
....................................................................................................................................
 
MESSAGE QUEUE NAME:  SYSTEM.TEMPORARY.QUEUE                          , MESSAGE QUEUE TYPE:  LOCAL
 
                        OPEN QUEUE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED OPENS PER SECOND
                       CLOSE QUEUE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED CLOSES PER SECOND
            ADD PERSISTENT MESSAGE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED PERSISTENT MESSAGES ADDED PER SECOND
         ADD NONPERSISTENT MESSAGE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED NONPERSISTENT MESSAGES ADDED PER SECOND
 
        ADDED PERSISTENT MESSAGE LENGTH:          0.00 MEAN,         0.00 MAXIMUM OBSERVED BYTES PER ADDED PERSISTENT MESSAGE
     ADDED NONPERSISTENT MESSAGE LENGTH:          0.00 MEAN,         0.00 MAXIMUM OBSERVED BYTES PER ADDED NONPERSISTENT MESSAGE
 
                            SWEEP COUNT:                                0 TOTAL OBSERVED SWEEPS DURING DATA COLLECTION RUN
 
T P F   M*Q*S E R I E S   M E S S A G E - Q U E U E   R E P O R T                04 MAR        14:29:43     MESSAGE    PAGE     2
 
BSS   SUBSYSTEM
 
==============
MESSAGE QUEUES FOR LOCAL QUEUE MANAGER:  TPFQM                                           ,   5 OBSERVATIONS,    24 SECONDS, CPU B
==============
 
MESSAGE QUEUE NAME:  XQ1                                             , MESSAGE QUEUE TYPE:  TRANSMISSION
 
            ADD PERSISTENT MESSAGE RATE:          0.00 MEAN,         0.00 MAXIMUM OBSERVED PERSISTENT MESSAGES ADDED PER SECOND
         ADD NONPERSISTENT MESSAGE RATE:          3.00 MEAN,        15.00 MAXIMUM OBSERVED NONPERSISTENT MESSAGES ADDED PER SECOND
 
        ADDED PERSISTENT MESSAGE LENGTH:          0.00 MEAN,         0.00 MAXIMUM OBSERVED BYTES PER ADDED PERSISTENT MESSAGE
     ADDED NONPERSISTENT MESSAGE LENGTH:         50.00 MEAN,        50.00 MAXIMUM OBSERVED BYTES PER ADDED NONPERSISTENT MESSAGE
 
                            SWEEP COUNT:                                0 TOTAL OBSERVED SWEEPS DURING DATA COLLECTION RUN
 
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
 
MESSAGE QUEUE  T O T A L S
 
                        OPEN QUEUE RATE:          0.04 TOTAL MEAN OBSERVED OPENS PER SECOND
                       CLOSE QUEUE RATE:          0.04 TOTAL MEAN OBSERVED CLOSES PER SECOND
            ADD PERSISTENT MESSAGE RATE:          3.00 TOTAL MEAN OBSERVED PERSISTENT MESSAGES ADDED PER SECOND
         ADD NONPERSISTENT MESSAGE RATE:          3.64 TOTAL MEAN OBSERVED NONPERSISTENT MESSAGES ADDED PER SECOND
 
        ADDED PERSISTENT MESSAGE LENGTH:         50.00 TOTAL MEAN OBSERVED BYTES PER ADDED PERSISTENT MESSAGE
     ADDED NONPERSISTENT MESSAGE LENGTH:         50.00 TOTAL MEAN OBSERVED BYTES PER ADDED NONPERSISTENT MESSAGE
 
                            SWEEP COUNT:             5 TOTAL OBSERVED SWEEPS DURING DATA COLLECTION RUN