Compaq AA-Q88CE-TE - Manual (Page 69)

RTR Monitoring
5.2 Standard Monitor Pictures
5.2.24 Monitor Rejhist
Rejected Transaction History
NODE: NODEA PROCESS: 38009A8B Mon Mar 9 1999 10:26:14
Time Chan Reason Status Text
------------------- ------ ------- --------------------------------------
Mon Mar 15 18:06:06 client 0 Client aborted tx
Mon Mar 15 18:06:41 server 0 Normal successful completion
Mon Mar 15 18:06:41 client 0 Server aborted tx
-------------------------------------------------------------------------------
number of reject msgs = 3
number of accept msgs = 0
rejected / total txns = 100%
Displays the last ten rtr_mt_rejected messages received by the selected process.
This picture should always be invoked with the /ID qualifier. The transaction
identifier associated with the rejected transaction can be displayed with the
SHOW PROCESS <
id >/COUNTER= api_reject* command.
Table 5–6 MONITOR REJHIST Fields
Field Meaning
Time Time of day that the rtr_mt_rejected message was generated.
Chan The type of channel (client or server) that received the message.
Reason The reason field returned in the rtr_status_data_t buffer.
Status Text The textual status that describes the reject reason.
5.2.25 Monitor Response
TRANSACTION DURATION AT 10:24:51 Fri Apr 9 1999
Process Image Client Response Time Server Response Time
ID Name seconds 0 1 2 3 4 seconds 0 1 2 3 4
20413894 SERVER.EXE;4 0.000 3.670
20417266 RTR.EXE;75 2.200 3.440
20417274 SERVER.EXE;4 0.000 1.160
Displays the elapsed time that a transaction has been active on the opened
channels of a process. On the client, transaction duration is measured
between the
rtr_start_tx or rtr_send_tx call and the receipt of the final
rtr_mt_accepted or rtr_mt_rejected message. A call to rtr_reject_tx
also marks the end of a transaction. On the server, transaction duration
is measured between receipt of a
rtr_mt_msg1 or rtr_mt_msg1_uncertain
message and the receipt of the final rtr_mt_rejected message or rtr_reject_tx
call. Accepted transaction end times are recorded when the server issues a
rtr_receive_message call to request a new transaction for processing.
RTR Monitoring 5–15