| Previous | Contents | Index |
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 messages: 3
number of accept messages: 0
rejected / total txns (%): 100%
This display should be invoked with the /ID qualifier.
|
Displays the last 10 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.
| Field | Meaning |
|---|---|
| Time | Time of day that the rtr_mt_rejected message was generated |
| Chan | Type of channel (client or server) that received the message |
| Reason | Reason field returned in the rtr_status_data_t buffer |
| Status Text | Textual status that describes the reject reason |
TRANSACTION DURATION AT 10:24:51 Fri Apr 9 1999
Process ID, Image Name Client Response Time Server Response Time
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 an
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 an
rtr_receive_message
call to request a new transaction for processing.
6.2.26 Monitor Rolequor
QUORUM COUNTS BY FACILITY Fri Sep 08 2000 14:32:48, NODE: -ALL-
Facility name Router View of Backend View of
Backends Routers Backend Routers
CNF RCH QRT CNF RCH QRT CNF RCH QRT CNF RCH QRT
RTR$DEFAULT_FACILITY 1 1 1 1 1 1 1 1 1 1 1 1
|
ROUTER TRANSACTION COUNTERS AT 14:33:29 Fri Sep 08 2000
Node: -ALL-
Facility: -ALL-
Count Rate 10 20 30 40 50 60 70 80 90 100
Starts: 116641 25.7
Enqueues: 116641 25.7
Commits: 116641 25.6
Aborts: 0 0.0
|
Displays information on a router node. It gives an indication of the
utilization of the router in terms of transactions and broadcasts
routed through this node. Useful to monitor performance or locate
problems. Uses counters in the Transaction Manager (TM) subsystem.
6.2.28 Monitor Routing
ROUTING STATISTICS BY FACILITY Thu Apr 15 1999 14:34:20, NODE: -ALL-
Facility name Transactions Broadcasts
Count Rate Count Rate
Total 118489 39.2 68444 994.0
RTR$DEFAULT_FACILITY 118489 39.2 68444 994.0
|
Displays statistics of transaction and broadcast traffic by facility.
Rate is the number of transactions or broadcasts per second within the
monitoring interval.
6.2.29 Monitor RSCBE
Most Recent RSC Dclsrv Calls History on Backend NODEA Thu Mar 4 1999,15:19:41
Partition name: RTR$DEFAULT Partition Start Time: THU MAR 4 15:18:22 1999
Image Name: RTR.EXE
T-delta RSC calls router state seq_nr
0 send_dcl_to_master nodez wait_for_response 0
1 recv_status_ok nodez rstart_rvy 1
1 send_dcl_to_master nodez rstart_rvy_incomp 1
1 recv_status_ok nodez rstart_rvy 1
1 send_dcl_to_master nodez rstart_rvy_incomp 1
1 recv_status_ok nodez active 1
1 send_dcl_to_other node10 active 1
1 recv_status_ok node10 active 1
|
Displays backend request to server messages and declared state for routers.
NETWORK STALLS AT Fri Sep 08 2000 15:35:03, ON NODE: TR1
Messages Bytes Link Stalls
Issued Rate Sent Drops Secs <3s <10s <30s >30s Totals
Total 5467 0.0 327148 2 33 23 1 0 0 24
TR1 -> TR1 29 0.0 3718 0 0 0 0 0 0 0
TR1 -> FE2 509 0.0 20707 0 4 4 0 0 0 4
TR1 -> BE1 303 0.0 13707 0 3 3 0 0 0 3
TR2 -> TR2 111 0.0 11682 0 0 0 0 0 0 0
TR2 -> BE1 504 0.0 22743 0 18 8 1 0 0 9
FE1 -> FE1 64 0.0 6645 0 0 0 0 0 0 0
FE1 -> FE2 373 0.0 18890 0 2 2 0 0 0 2
FE1 -> BE1 310 0.0 24487 0 0 0 0 0 0 0
FE2 -> FE2 231 0.0 18900 0 0 0 0 0 0 0
FE2 -> BE1 284 0.0 22503 1 1 1 0 0 0 1
FE2 -> TR1 536 0.0 28166 0 0 0 0 0 0 0
FE2 -> FE1 396 0.0 23643 0 0 0 0 0 0 0
BE1 -> BE1 355 0.0 28121 0 0 0 0 0 0 0
BE1 -> FE2 284 0.0 13014 1 0 0 0 0 0 0
BE1 -> TR2 515 0.0 27502 0 2 2 0 0 0 2
BE1 -> TR1 328 0.0 25698 0 1 1 0 0 0 1
BE1 -> FE1 335 0.0 17022 0 2 2 0 0 0 2
|
Displays in real time any network links that are currently stalling (that is, waiting to transmit outbound traffic) and provides a history of the stalls encountered by the various links during their lifetime. The display shows:
System Status at 10:27:51 Fri Apr 9 1999
node: NODEA
Resource OK Warning
Facility QUORUM states...... x
JOURNAL free space.......... x
Link CONNECTS............... x
Link traffic STALLS......... x
FLOW control credits........ x
PARTITION states............ x
CALL Msg outstanding.......... x
Transaction QUEUES............ x
Transaction REJECTS........... x
Broadcast EVENT discards...... x
For additional detail about a resource,
monitor the appropriate subsystem. To
customize threshold values, edit
SYSTEM.MON. If viewing this page in a
browser, follow the hyperlinks above.
|
Displays the state of critical resources within the RTR environment. If a resource has exceeded a predefined threshold, a warning indicator is displayed.
The default thresholds are as follows:
| Quorum | Warns if any roles are inquorate |
| Journal | Warns if journal free space is less than 30% of total |
| Links | Warns if any link is disconnected |
| Stalls | Warns if 10 second stalls are greater than 1% of all messages sent |
| Flow | Warns if the wait is more than 1 second for 10% of the total credit requests |
| Partition | Warns if any of the partitions are not in one of the following states: Standby, Active, Pri_act, or Sec_act |
| Calls | Warns if any messages have been pending for more than 30 seconds |
| Queues | Warns if the transaction queue cannot be emptied within 10 seconds |
| Rejects | Warns if the number of rejects (non-user) is greater than 5% of the total transactions processed, or a reject (non-user) has occurred within the last 30 minutes |
| Events | Warns if the number of discards is greater than 5% of the total events sent |
Threshold values can be customized by editing the file SYSTEM.MON.
6.2.32 Monitor TPS
TRANSACTION COMMITS BY PROCESS 14:12:48 Wed Nov 3 1999 on nodeA
Commits Each # is 10tps
Node, Process ID & name Absolute Rate/s 50 100 150 200 250 300
nodeA -ALL- -CLIENTS- 2401 45.0 ####
nodeA -ALL- -SERVERS- 2401 45.0 ####
nodeA 22941 smith_1 2401 45.0 ####
nodeA 22933 jones_1 2401 45.0 ####
|
Displays the transaction processing rate of each process on a system.
The cumulative total for all client and all server processes is also
given.
6.2.33 Monitor TPSLO
TRANSACTION COMMITS BY PROCESS 14:12:48 Wed Nov 3 1999 on nodeA.zko.dec.com
Commits
Node ID Process Abs. Rate | 2 4 6 8 10
nodeA -ALL- -CLIENTS- 5 2.0 ##
nodeA -ALL- -SERVERS- 5 2.0 ##
nodeA 22941 smith_1 10 4.0 ####
|
Displays low end of the rate of transaction commits carried out by each
process using RTR. It is intended for systems with throughput less than
10 tps.
6.2.34 Monitor Traffic
LINK TRAFFIC Fri Sep 08 2000 14:38:08, NODE: -ALL-
Bytes/sec Packets/sec Messages/sec Congestion
Rcvd Sent Rcvd Sent Avrg Rcvd Sent Count Rate
Total 13465.5 13213.3 123.8 121.2 239.1 53.3 53.3 35 0.0
NODEA -> NODEA 0.0 0.0 0.0 0.0 0.0 0.0 0.0 0 0.0
NODEA -> NODEB 10718.0 2705.8 95.1 27.5 118.9 24.9 27.2 28 0.0
NODEB -> NODEB 41.7 41.7 1.2 1.2 1.4 1.2 1.2 0 0.0
NODEB -> NODEA 2705.8 10465.8 27.5 92.5 118.8 27.2 24.9 7 0.0
|
Displays a list of the links to other nodes. Shown for each link are:
byte rate, packet rate, message rate and congestion, in both
directions. Average packets per second is also shown. Uses counters in
the Network I/O (NIO) subsystem.
6.2.35 Monitor Trans
Monitoring transactions Thu Mar 4 1999 15:21:38, NODE: NODEA Transaction ID (Frontend) Facility FE-UserState 46d01f10,0,0,0,0,baa09da,abf10001 RTR$DEFAULT_FACILITY RTRCSV_TETRAUL aborting Transaction ID (router) Facility FE-UserState State Transaction ID (backend) Facility FE-UserState 46d01f10,0,0,0,0,baa09da,abf10001 RTR$DEFAULT_FACILITY RTRCSV_TETRAUL aborting |
Displays transaction state for transactions in a facility.
6.2.36 Monitor V2CALLS
RTR V2 system service calls, Node: NODEA , PID: 00000000, Process name: -ALL-
Image: -ALL- 13:09:18 5-MAR-1999
Accept Reject Success Failure Outstng Calls
dcl_tx_prc/server 3 0 4 0 0 4
dcl_tx_prc/req. 1
dcl_tx_prc/shut. 0
start_tx 1 0 1 0 0 1
start_tx /timeout 0
enq_tx 1 0 50395 0 0 50395
enq_tx /broadcast 25187
enq_tx /reply 25207
deq_tx 50381 0 50391 0 2 50393
deq_tx /reply 12
commit_tx 1 0 1 0 0 1
abort_tx 0 0 0 0 0 0
vote_tx /commit 25187 0 25189 0 0 25189
vote_tx /abort 0
vote_tx /forget 2
|
Displays calls made by applications to the Version 2.0 API.
6.2.37 Monitor XA
RTR XA Calls Node: nodea.zko PID: -ALL- Process name: -ALL-
Image: -ALL- 11:42:06 Tue 6-Apr-1999
XA Verb Name Calls Success Readonly Failure
open 0 0 0 0
close 0 0 0 0
start 0 0 0 0
end 0 0 0 0
prepare 0 0 0 0
commit 0 0 0 0
rollback 0 0 0 0
recovery 0 0 0 0
Rate 0 2 4 6 8 10 12 14 16 18 20 Active
txn starts 0.0 0
|
Displays XA calls when using XA with RTR.
Each RTR API call can be invoked at CLI level using the RTR command utility. This is provided to facilitate testing. For example, clients can be tested before the corresponding servers have been written by manually entering the server's API calls.
The most commonly used RTR commands can also be invoked using the RTR web browser interface. The available commands include those used by a developer in a development environment as well as commands that allow you to monitor the operation of a production system. See Section 1.2.1 for instructions on how to use the RTR web browser interface.
7.1 Introduction
The commands that invoke the RTR API calls are similar to the call
names. For example, the
rtr_accept_tx()
call is invoked using CALL RTR_ACCEPT_TX at the CLI level.
Where possible, command qualifiers have been given the same names as the parameters to the API calls. See the C Application Programmer's Reference Manual for details about the parameters to API calls.
Most commands can be issued on remote nodes by using the /NODE=node-list or /CLUSTER qualifiers, or by preceding them with the SET ENVIRONMENT command to specify nodes where commands are to be executed. Commands such as DEFINE KEY are intended for local execution only.
Output from each command can be redirected to another device or file using the /OUTPUT qualifier.
Because the RTR command utility keeps parameter checking to a minimum, "what if" questions can be answered quickly without having to write test programs.
In a mixed RTR Version 2 and Version 3 or Version 4 environment, you cannot execute commands remotely with the /NODE qualifier. You can use the qualifier in a mixed Version 3 and Version 4 environment. |
This section describes in detail each command in the RTR command utility.
The command descriptions are presented in alphabetical order.
See CREATE FACILITY; ADD FACILITY is retained for compatibility reasons only.
The CALL RTR_ACCEPT_TX command causes a command server to execute the rtr_accept_tx() routine and to display the returned status.
CALL RTR_ACCEPT_TX
| Command Qualifiers | Defaults |
|---|---|
| /CHANNEL_NAME=channel-name | /CHANNEL_NAME=RTR$DEFAULT_CHANNEL |
| /CLUSTER | /NOCLUSTER |
| /FORGET | /NOFORGET |
| /INDEPENDENT | /NOINDEPENDENT |
| /NODE[=node-list] | /NODE=default-node |
| /OUTPUT[=filespec] | /OUTPUT=stdout |
| /REASON[=reason] | /REASON=0 |
The CALL RTR_ACCEPT_TX command causes a command server to call the rtr_accept_tx() routine using values supplied on the command line.The numeric status returned from the call is then converted to its textual representation and displayed.
The rtr_accept_tx() routine itself is described in the C Application Programmer's Reference Manual.
The prototype of rtr_accept_tx() is:
rtr_status_t rtr_accept_tx ( rtr_channel_t channel, rtr_acc_flag_t flags, rtr_reason_t reason ) ;Table 7-1 shows the correspondence between values you supply on the command line and the C language parameter values produced and used for the call.
Table 7-1 Parameters for rtr_accept_tx C Parameter Name C Parameter Value Command Line Specification channel /CHANNEL_NAME=name flags RTR_NO_FLAGS [none] [D] RTR_F_ACC_FORGET /FORGET reason RTR_NO_REASON /NOREASON [D] reason_value /REASON=reason_value Issuing the CALL RTR_ACCEPT_TX command in preference to using the /ACCEPT qualifier with the CALL RTR_SEND_TO_SERVER or CALL RTR_REPLY_TO_CLIENT commands is only necessary when specifying an acceptance "reason" other than the default value of zero (using the /REASON qualifier).
/CHANNEL_NAME=channel_name
/CHANNEL_NAME=RTR$DEFAULT_CHANNEL
Specifies the channel for which the operation is to be performed.The command server uses a combination of the channel name and the window from which the call was issued to uniquely identify which channel to use.
channel_name is not case sensitive.
The default for channel_name is RTR$DEFAULT_CHANNEL.
/CLUSTER
/NOCLUSTER (D)
Specifies that the command is executed on all the nodes in the cluster.If neither /NODE nor /CLUSTER is specified, the command is executed on the nodes specified by the latest SET ENVIRONMENT command. If no SET ENVIRONMENT command has been entered, the command is executed only on the node where the command was issued.
Note
In environments that do not support clustering, the /CLUSTER qualifier causes the relevant command to be executed on the local node only./FORGET
/NOFORGET
Use /FORGET to specify the flags parameter as RTR_F_ACC_FORGET in the call rtr_accept_tx() .The default value for /FORGET is /NOFORGET, which causes the command server to use the value RTR_NO_FLAGS for the flags parameter in the call to rtr_accept_tx() .
/INDEPENDENT
/NOINDEPENDENT
Use the /INDEPENDENT qualifier to specify the flags parameter RTR_F_ACC_INDEPENDENT in the call to rtr_accept_tx() ./NODE[=node-list]
/NODE=default-node (D)
Specifies that the command is executed on all nodes specified in node-list . If node-list is omitted, the command is executed only on the node where the command was issued./OUTPUT[=filespec]
/OUTPUT=stdout (D)
Specifies that the resulting information is written to the file filespec . If /OUTPUT or filespec is omitted, the standard or default output is used./REASON[=reason]
/REASON=0
Use /REASON to supply a value for the reason parameter in the call to rtr_accept_tx() .The default value for /REASON is 0, which causes the command server to use the value RTR_NO_REASON for the reason parameter in the call to rtr_accept_tx() .
Accept the current transaction with a reason of 42.
RTR> CALL RTR_ACCEPT_TX /REASON=42
%RTR-S-OK, normal successful completion
|
| Previous | Next | Contents | Index |