Transaction Response report description
The folowing table describes Transaction Response report elements.
The reference numbers (with the n format) match the elements in the report example pages to the elements described in the table.
Transaction Response report elements
Ref. | Description |
---|---|
1 | CURRENT DATE Date this report was generated, in mm/dd/yy format |
2 | Title Title that identifies the type of report |
3 | REPORTING RANGE REQUESTED Time range requested for this response report This range is the same as the range specified with the PARM option in the EXEC statement. If the time range selection was not specified, this range is set to equal the ACTUAL REPORTING RANGE FOUND. The range is expressed as the lowest date (yy.ddd) and time (hh.mm) requested through the highest date (yy.ddd) and time (hh. mm) requested. |
4 | ACTUAL REPORTING RANGE FOUND Time range encountered for this response report This range is expressed as the lowest date (yy.ddd) and time (hh.mm) found in the data selected for reporting through the highest date yy.ddd) and time (hh.mm) found in the data selected. |
5 | TRANCODE LTERM Major (total) and minor (subtotal) control break fields for Transaction Response reports Other control break fields are as follows:
|
6 | Control break fields Major and minor control break fields are shown at each change. Minor control break lines can be suppressed. Consequently, the minor field displays the word TOTAL (which corresponds to the major reporting level chosen). The sum of all totals for a report type is shown as FINAL TOTALS. The fields are:
|
7 a | TOTAL ACCOUNTED Total number of transaction records processed within this reporting level |
8 a | TOTAL ACCOUNTED (with valid timing) Number of transaction records processed within this reporting level that had a valid timing of this type For example, if a transaction made no response to the originating terminal, the transaction would not be included in the response count, nor would it be used to calculate the average and cumulative range percentages. This transaction would, however, appear in the input queue and elapsed time counts. If no transactions within the reporting level had a requested timing (RESPONSE), that timing is not printed. |
9 a | AVG. SECS (W/O OVER) Average number of microseconds calculated for this timing; total accumulated seconds divided by the total accounted for this timing, excluding any values in the last range If all values for this timing fall in the last range, the average is not calculated and this field is blank. |
10 a | RANGES IN SECONDS (UPPER LIMITS) Upper limit of each range in the distribution is shown in tenths of a second, as specified by the RSRANG control statement (see Time range specification) A maximum of eleven ranges can be reported. The last range contains any values that exceed the last upper limit defined. Within each range, the following fields are shown for each timing requested for that report type, at each reporting level (control break):
|
11 a | **MSG SWS Number of transactions that were message switches (reported only with the ARIV START and ARIV STOP timings); number of transactions that made a response that was a message switch (reported only with the RESPONSE timing) This report element is available only if the IMFLEDIT RSPOPT parameter is set to RSPOPT=YES. |
12 a | **MSG SW AVG LEVEL Average level of message switching to reach this transaction For example, a value of 1 indicates that the program processing the originating transaction from the terminal created this transaction as a message switch. A value of 2 indicates that another program was also invoked. (Reported only with the RESPONSE, ARIV START, or ARIV STOP timings.) This report element is available only if the IMFLEDIT RSPOPT parameter is set to RSPOPT=YES. |
13 b | RESPONSE Arrival time to message sent time For message switches, the arrival time of the original input transaction is used. You can set a parameter in IMFLEP00 to limit this time to a maximum value (seeMainView for IMS and MainView for DBCTL Customization). For DBCTL threads and TPI, this field is zero. This report element is available only if the IMFLEDIT RSPOPT parameter is set to RSPOPT=YES. |
14 b | INPUT Q Arrival time to start time For message switches, the enqueue time of the message switch transaction is used. You can set a parameter in IMFLEP00 to limit this time to a maximum value (seeMainView for IMS and MainView for DBCTL Customization). For DBCTL threads and TPI, this field is zero. |
15 b | ELAPSED Start time to stop time In most situations the elapsed time should be smaller than the response time. In some situations, however, a transaction program can have a lengthy logic path from the time an output is inserted to the I/O PCB and the GU on I/O PCB for the next message. For example, the 2-phase commit can take a long time. |
16 b | RSP TO DEQ Arrival time to message free time
This report element is available only if the IMFLEDIT RSPOPT parameter is set to RSPOPT=YES. |
17 b | OUTPUT Q Message insert time to message sent time For DBCTL threads and TPI, this field is zero. This report element is available only if the IMFLEDIT RSPOPT parameter is set to RSPOPT=YES. |
18 b | DEQUEUE Message sent time to message free time This report element is available only if the IMFLEDIT RSPOPT parameter is set to RSPOPT=YES. |
19 b | OUT TO DEQ Message insert time to message free time For DBCTL threads and TPI, this field is zero. This report element is available only if the IMFLEDIT RSPOPT parameter is set to RSPOPT=YES. |
20 b | ARIV-START Arrival time to start time For message switches, the arrival time of the original input transaction is used (original to MainView for IMS input queue time definition). You can set a parameter in IMFLEP00 to limit this time to a maximum value (seeMainView for IMS and MainView for DBCTL Customization). For DBCTL threads and TPI, this field is zero. |
21 b | ARIV-STOP Arrival time to stop time For message switches, the arrival time of the original input transaction is used (original MainView for IMS response time definition). |
|
Related topic