This report contains data on response times, think times, transaction times and wait times for messages in the BCAM pool.
Report output
The REPORT RESPONSE statement is used to request the output of the RESPONSETIME report.
The report can only be output if the SM2 administrator has
defined the monitoring parameters using the SET-RESPONSETIME-PARAMETERS statement
specified the connection sets to be monitored using the ADD-CONNECTION-SET statement
activated the monitoring process using the statement START-MEASUREMENT-PROGRAM TYPE=*RESPONSETIME
Depending on the definition of the SCOPE operand in the SET-RESPONSETIME-PARAMETERS or MODIFY-RESPONSETIME-PARAMETERS statement, SM2 output bucket-specific or category-specific screens.
In the case of SCOPE=*BUCKET, the user receives a separate screen for each of the connection sets to be monitored (up to 16, including global statistics) with bucket-specific values. Global statistics are output first.
In the case of SCOPE=*CATEGORY, the user receives a separate screen for each of the connection sets to be monitored (up to 16, including global statistics) with category-specific values. Global statistics are output first.
Categories for which no values have been specified are not output. If values are specified for more than 13 categories, the screen is scrolled upwards by the corresponding number of lines so that the topmost lines of the report are not visible on the screen.
If both SCOPE=*CATEGORY and SCOPE=*BUCKET are specified, a screen is output for bucket-specific values first, followed by one for category-specific values.
Bucket-specific screen
HOST0001 SM2 RESPONSETIME (BUCKETS) CYCLE: 60 S <date> <time>
*GLOBAL APPLICATION: *ALL
PARTNER: *ALL
CONN-TYPE:REMOTE PROCESSOR: *ALL
---------------------------+----------------+----------------+----------------+
| RESP. TIME (1) | THINK TIME | TRANS. TIME | WAIT TIME |
+----------------+----------------+----------------+----------------+
| BUCKET COUNT | BUCKET COUNT | BUCKET COUNT | BUCKET COUNT |
+----------------+----------------+----------------+----------------+
| 0.5 4386 | 5.0 4393 | 0.5 4357 | 0.1 345 |
| 1.0 8 | 15.0 21 | 1.0 11 | 0.2 0 |
| 2.0 8 | 30.0 4 | 2.0 7 | 0.5 0 |
| 5.0 11 | 60.0 1 | 5.0 16 | 1.0 0 |
| 10.0 3 | 120.0 8 | 10.0 11 | 2.0 0 |
|> 10.0 18 |> 120.0 7 |> 10.0 32 |> 2.0 0 |
----------+----------------+----------------+----------------+----------------+
AVG SEC | 0.1 | 0.3 | 0.1 | 0.0 |
NR. INTER | 4416 | 4427 | 4402 | 345 |
RATE 1/SEC| 76.1 | 76.3 | 75.9 | 5.9 |
----------+----------------+----------------+----------------+----------------+
INPUT-LEN:570.7 OUTPUT-LEN:451.7
Monitoring information
For each screen, the associated connections or connection groups are output above the monitoring data, as well as the connection set name (“GLOBAL” is the name given in the example), when the ADD-CONNECTION-SET statement is defined).
CONN-TYPE | Types of connections taken into account during monitoring:
|
RESP. TIME (1) | Response time data; the type of response time monitored (as specified via the DEFINITION operand of the SET- and MODIFY- RESPONSETIME-PARAMETERS statements) is output (1): Response time as per definition 1 (2): Response time as per definition 2 |
THINK TIME | Think time data |
TRANS. TIME | Transaction time data |
WAIT TIME | Wait time data (in the BCAM pool) |
AVG SEC | Average duration of an interaction in seconds (without overflow data) |
NR. INTER | Total number of interactions in the monitoring cycle (without overflow data) |
RATE 1/SEC | Number of monitored interactions per second (without overflow data) |
BUCKET | Corresponds to the bucket limits in seconds in which monitored data is arranged in accordance with duration. The last line of the columns (>) contains the overflow data. Data displayed there is not is not used for computing AVG SEC, NR. INTER and RATE 1/SEC. |
COUNT | Corresponds to the number of interactive operations in the individual buckets |
The SM2 administrators can modify the bucket limits and the number of buckets by means of the SET- and MODIFY-RESPONSETIME-PARAMETERS statements if the default options are not suitable. If no interactions were recorded in the last monitoring cycle, the message NOTE: SOME INTERACTIONS MISSED:<number> is displayed in the bottom line of each of the RESPONSE TIME screens. This may be the case, for example, if the number of active connections is greater than that defined in the CONNECTION-NUMBER parameter of the SET- or MODIFY-RESPONSETIME-PARAMETERS statement. | |
INPUT-LEN OUTPUT-LEN | The average lengths in bytes of the input or output messages |
Category-specific screen
HOST0001 SM2 RESPONSETIME (CATEGORY) CYCLE: 60 S <date> <time>
*GLOBAL APPLICATION: *ALL
PARTNER: *ALL
CONN-TYPE:REMOTE PROCESSOR: *ALL
CATGORY| RESPONSE TIME | THINK TIME |TRANSACTION TIME | WAIT TIME
NAME | AVG #INT RATE| AVG #INT RATE| AVG #INT RATE| AVG #INT RATE
-------+-----------------+-----------------+-----------------+-----------------
SUM | 0.1 4416 76.1| 0.3 4427 76.3| 0.1 4402 75.9| 0.0 345 5.9
SYS | 0.1 78 1.3| 8.9 85 1.5| 0.1 4328 74.6| 0.0 150 2.6
BATCH | 0.1 1456 25.1| 0.0 1457 25.1| 0.0 0 0.0| 0.0 0 0.0
TP | 0.9 33 0.6| 2.6 38 0.7| 1.0 31 0.5| 0.0 15 0.3
BATCHF | 0.0 422 7.3| 0.0 423 7.3| 0.0 2 0.0| 0.0 180 3.1
DIALOG1| 0.1 310 5.3| 0.7 306 5.3| 0.2 41 0.7| 0.0 0 0.0
DIALOG2| 0.1 2117 36.5| 0.1 2118 36.5| 0.0 0 0.0| 0.0 0 0.0
Monitoring information
For each screen the associated connections or connection groups are output over the monitoring values; the connection set name (in the example it is *GLOBAL) is output, too. (A connection set with the name *GLOBAL, in which all connections are monitored (CONNECTION (*ALL,*ALL,*ALL)), is automatically defined using the SET-RESPONSETIME-PARAMETERS statement.)
CONN-TYPE: | Types of connections taken into account during monitoring:
|
CATGORY NAME | Name of the category |
RESPONSETIME | Monitoring data for the response time |
THINK TIME | Monitoring data for the think time |
TRANSACTION TIME | Monitoring data for the transaction time |
WAIT TIME | Monitoring data for the wait times (in the BCAM pool) |
AVG | Average duration of the transaction (in seconds) (without overflow values) |
#INT | Total number of transactions during the monitoring cycle (without overflow values) |
RATE | Number of interactions monitored per second (without overflow values) |