gtps3m0m | System Performance and Measurement Reference |
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
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
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
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
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
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
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.
Figure 60. Message Stream Report by LU
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.
Figure 61. Message Stream Report by Agent
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.
Figure 62. Distributed Data Management (DDM) Message Stream 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 name of the application. The application must be defined in the TCP/IP network services database. If an application is not defined in the database, the number of messages is shown in the OTHER category. See TPF Transmission Control Protocol/Internet Protocol for more information about defining applications in the TCP/IP network services database.
The port associated with this application.
The weighting factor used when counting the input messages for this application. This weighting factor can be defined for each application in the TCP/IP network services database by specifying the weight parameter. If a weighting factor is not defined for the application, this column contains asterisks (***). See TPF Transmission Control Protocol/Internet Protocol for more information about defining applications in the TCP/IP network services database and how message counts are incremented for TCP/IP applications.
The number of messages that were received by this application each second. These are raw message counts; that is, they are not weighted.
The number of packets containing data that were received by this application each second.
The number of bytes that were received by this application each second.
The number of messages that were sent by this application each second. These are raw message counts; that is, they are not weighted.
The number of packets containing data that were sent by this application each second.
The number of bytes that were sent by this application each second.
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 |
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:
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 |