hp Reliable Transaction Router
System Manager's Manual


Previous Contents Index

7.2.6 Monitor Broadcast

Displays information about the RTR user events process. Fields displayed include number of user events enqueued for the application, number of user events received by the application, and number of user events discarded by RTR.

Example 7-6 Monitor Broadcast

                BROADCAST RECEPTION BY PROCESS 15:20:27   6-APR-1999 
 
Node      ID    Process name   Received Queued  Lost       Delivery Rate 
Total                              2750     5     17               850.0 
 
NODEA  20400249 SMITH RTR             0     0      0 
NODEA  2040024D JONES RTR          2750     5     17               850.0 
NODEA  2040024B BROWN RTR             0     0      0 
NODEA  2040024C ALLEN RTR             0     0      0 

7.2.7 Monitor Calls

Displays the total number of RTR API calls and their outcome for the processes on all the nodes being monitored. Use the /IDENTIFICATION= process-id qualifier to display the values for one specific process, otherwise the total values for all processes are displayed.

Example 7-7 Monitor Calls

RTR API calls, Node: nodea             , PID: 2162    , Process name: -ALL- 
Image: -ALL-                                        16:38:05 Tue Dec 04 2001 
CALLS            Client   server  fail  MESSAGES        client   server  pend 
open_channel         11        7    18  mt_opened            4        3     4 
close_channel         5        3     0  mt_closed            0        1     0 
start_tx              2        -     4  mt_msg1              -        0     2 
send_to_server        5        -     2  mt_msg1_uncertain    -        0     0 
                                        mt_msgn              -        0     3 
reply_to_client       -        0     4  mt_reply             0        0     0 
                                        mt_rettosend         0        -     0 
prepare_tx            0        -     0  mt_prepared          0        -     0   
accept_tx             0        0     0  mt_accepted          0        0     0 
reject_tx             0        0     0  mt_rejected          0        0     1 
broadcast_event       0        0     0  mt_user_event        0        0     0 
set_user_handle       0        0     0  mt_rtr_event         0        0     0 
get_tid               0        0     0  mt_prepare           -        0     0 
                  other                                   other 
request_info          3        -     1  mt_request_info      2        -     0 
set_info              0        -     0  mt_set_info          0        -     0 
error_text            2                 mt_closed            2 
set_wakeup            0 
                  calls   active     fail  timeout 
receive_message       9        1        2        2 
user wakeup           0        0 
 

7.2.8 Monitor Channel

Displays the channels opened by the CALL RTR_OPEN_CHANNEL command.

OpenVMS systems show the actual process names; on Windows and UNIX systems RTR produces a process name by combining user name and image name.

Example 7-8 Monitor Channel

RTR CHANNELS BY TYPE PER PROCESS  16:41:13 Tue Dec 04 2001 
                    
                                                               Call-out 
Node     ID   Process name   Image name  Client    Server    Router  Backend 
Nodea  2162   SMITH_1        DISK01:[SMI... 6         3           0        0 

7.2.9 Monitor Connects

Displays the link protocol for connected links, and the fail reason as a text message for any links on which a connection has failed. Unconnected links where connection has been attempted are highlighted. Link state and architecture of the remote node are also displayed. Summarizes link status and is less detailed than the MONITOR NETSTAT display.

Example 7-9 Monitor Connects

 
               C o n n e c t i o n   S t a t u s   S u m m a r y 
 
           Node: nodea                    Tue Feb 16 1999 13:02:18 
 
Executive summary--------------------------------------- 
                Number of links up:     3        
            Number of links up (%):   100.0 
                 Required links up:   Yes 
         ------------------------------------------------ 
 
-Detail- 
 Node -> Link  State  Arch T'port Fail-reason 
--------------:-----:-----:------:-------------------------------- 
nodea->nodea      up alpha      - 
nodea->nodeb      up alpha    TCP 
nodea->nodec      up  i386    TCP 
 

7.2.10 Monitor Ctccalls

Displays the history of calls for a specific client transaction controller. Valid only when the application is using the C++ API.

Example 7-10 Monitor Ctccalls

 
 ORTR Call history monitor screen on node:walkin               PID : -ALL- 
Image: -ALL-                                     at 16:48:32 Mon Jul 16 2001_ 
 Calls         Channel #                  State     Msg/Event    Ch.Used  Status 
 

7.2.11 Monitor Downstream

Displays counts of flow-control induced traffic stalls downstream from the backend, between the backend and the router, and between the router and the frontend. Downstream traffic runs away from the backend.

Example 7-11 Monitor Downstream

FLOW CONTROL STALLS DOWNSTREAM BY NODE & FACILITY Mon Jul 16 2001 15:40:21, NODE 
 
                                    Txn traffic       Bdcst traffic 
                                be->tr     tr->fe        be->tr 
Node  & Facility              reqs stall  reqs stall  reqs stall 
rtrdoc   Test 

7.2.12 Monitor Event

Displays event routing data by facility. Information includes events in transit from RTR to a destination facility and destination information showing number of events enqueued for the application (In column), number of events processed by the application (Out column), and the number of events discarded by RTR (Lost column).

Example 7-12 Monitor Event

  
       EVENT ROUTING STATISTICS BY FACILITY  Fri Sep 08 2000 15:21:47 
 
                                 Destination              Transit 
Node & Facility                In    Out    Lost        In    Out    Lost 
Total                         180    175       5       180    180       0 
 
NODEA   FACCMS                 25     25       0        25     25       0 
NODEA   TESTFAC               155    150       5       155    155       0 

7.2.13 Monitor FastRecovery

Displays information on the number of transactions received in several recovery stages.

Example 7-13 Monitor FastRecovery

 
RECOVERY INFORMATION at Tue Dec 04 2001 09:57:51, on NodeA 
 
                      Last      Currnt Restart  CTR     Total    Shadow-Recovery 
           Server     Rcvy      Txns   Txns     Txns    CTR      Classic Copied 
Partition  State      Backend   Rcvd   Rcvd     Rcvd    Rcvd     Rcvd    Rcvd 
---------- ---------- ------    ------ -------  -----   ----- -- ------- ------ 
RTR$DEFAUL active     NODEA   1      0       0      0       0  0       0      0 

7.2.14 Monitor Flostalls

Displays counts of flow-control-induced traffic stalls.

Example 7-14 Monitor Flostalls

FLOW CONTROL INDUCED STALLS BY FACILITY Mon Jul 16 2001 15:41:03, NODE: rtrdoc 
 
                                 Request traffic           Response traffic 
                                fe->tr     tr->be          be->tr    tr->fe 
Node  & Facility              reqs stall  reqs stall     reqs stall reqs stall 
rtrdoc    Test 
 

7.2.15 Monitor Flow

Displays flow control internals.

Example 7-15 Monitor Flow

FLOW CONTROL COUNTERS  Tue Sep 19 2000 14:08:06, NODE: -ALL- , FAC: -ALL- 
 
        Credit      Data Rate             Requests                  Grants 
Role   Available    Bytes/sec        Waits   Sent  Pending       Sent  Pending 
FE=>TR     15000         2065          307    966        0        966        0 
TR=>BE     15000         2065           70    998        0        998        0 
BE=>TR         0            0            0      0        0          0        0 
TR=>FE     15000            0            0      2                   2        0 
 
 Link         Data Rate      Waits     Pending   Reqs Sent      Cache in use 
NODEA =>NODEA         0          0           0           1      NODEA        0 
NODEA =>NODEB         0          0           0           0      NODEB    51456 
NODEB =>NODEB      2065        307           0         968 
NODEB =>NODEA      2065         70           0         999 

7.2.16 Monitor Frontend

Displays frontend status and counts by node and facility, including frontend state, current router, reject status, retry count, and quorum rejects.

Example 7-16 Monitor Frontend

FRONTEND STATUS BY NODE AND FACILITY Tue Dec 04 2001 10:46:24, NODE:NODEA 
 
Node    Facility                       FE             Reject   Retry   Quorum 
                                     State   Router   Status   Count  Rejects 
NODEA   RTR$DEFAULT_FACILITY      cnctd to    smith                2        0 
NODEA   funds_transfer            cnctd to    smith                2        0 
NODEA   payroll                   waiting             no_qrum    395        0 

7.2.17 Monitor Group

Shows server and transaction concurrency by partition.

Example 7-17 Monitor Group

 
  Concurrency Measures    Tue Dec 04 2001 10:04:26, NODE: NODEA 
 
                                                              --  averages -- 
                          txn  -server-  --  transactions --  srv   txn   txn 
Partition     state     cnt  cnt  act  vreq vote  ack /csn    act  /sec  /csn 
RTR$DEFAULT   active      2    3    1     0    0    0    0    1.0   0.0   0.0 

Table 7-2 MONITOR GROUP Fields
Field Meaning
Partition Partition
state Partition state.
txn cnt Number of transactions executed for this partition.
srv cnt Number of servers active for this partition.
srv act Number of servers currently busy processing transactions for this sample.
The following fields track the progress of a transaction through the states: vote requested, voted, acknowledged.
vreq Number of transactions waiting for the server to vote.
vote Number of transactions that have been voted on by the server but not committed by RTR.
ack Number of transactions that have been committed but have not been acknowledged by the server. Acknowledgment occurs on a subsequent rtr_receive_message() call by the server processing this transaction to get a message for a new transaction.
/csn Number of transactions which have been grouped under the same "commit sequence number" (CSN). This grouping determines the ordering of transactions submitted to a secondary shadow server.
txn/sec The average rate of transaction starts per second for this partition.
txn/csn Average number of transactions which have been grouped under the same commit sequence number (CSN) since this partition became active. This average is computed as the quotient of the txn cnt column and the total number of CSNs.

7.2.18 Monitor Ipc

Displays interprocess communication message information.

Example 7-18 Monitor Ipc

 
Node: NODE11               I P C   S u m m a r y    Fri Mar  5 1999 11:18:34 
 
 +-------------------------------------------------------------------------+ 
  This screen displays usage information on IPC messages, byte counts and IO 
  primitives. Display units are counts, kbytes and calls respectively. 
 +-------------------------------------------------------------------------+ 
 
 
       | - - - - - O u t g o i n g / s - - - - | - - I n c o m i n g / s - -| 
Process   Messages ...kbytes   send() ...kbytes  Messages   recv() ...kbytes 
rtracp      110334     49744    73437     49744     73434   220299      5616 
3123B84F         0         0        0         0         0        0         0 
31232395     73282      5569    73280      5569    109930   293144     49685 
 

7.2.19 Monitor Ipcrate

Displays information on interprocess communication message rates.

Example 7-19 Monitor Ipcrate

 
Node: NODE11               I P C    R a t e s       Fri Mar  5 1999 11:18:53 
 
 +-------------------------------------------------------------------------+ 
  This screen displays rate information on IPC messages, byte counts and IO 
  primitive usage. Display units are counts, kbytes and calls per second 
  respectively. 
 +-------------------------------------------------------------------------+ 
 
       | - - - - - O u t g o i n g / s - - - - | - - I n c o m i n g / s - -| 
Process   Messages ...kbytes   send() ...kbytes  Messages   recv() ...kbytes 
rtracp          44        19       29        19        29       86         2 
3123B84F         0         0        0         0         0        0         0 
31232395        28         2       28         2        41      110        18 

7.2.20 Monitor Jcalls

Displays counts of successful (success), failed (fail) and total journal calls for local and remote journals.

Example 7-20 Monitor Jcalls

 
JOURNAL CALLS ON NODE NODEA             AT 11:25:44 Wed Jan 02 2002 
 
                      Local Journal               Remote Journal 
Journal API           Success      Fail  Total Success         Fail     Total 
   OPEN_JOURNAL             1         0      1          0         0         0 
   CLOSE_JOURNAL            0         0      0          0         0         0 
   READ_RECORD              4         0      4          0         0         0 
   READ_NEXT RECORD         2         3      4          0         0         0 
   GET_USAGE             4302         0   4303          0         0         0 
   WRITE_RECORD             5         0      5          0         0         0 
   FLUSH_TO_DISK            5         0      5          0         0         0 
   DELETE_RECORD            1         0      1          0         0         0 
 
                          #        BLOCKS            #         BLOCKS 
   EXTENDS                  0         0                 0         0 
   TRUNCATES                0         0                 0         0 
 

7.2.21 Monitor Jhuse

In the browser interface, displays the same information (bar graphs of usage for local and remote journals) as the MONITOR JUSE command displays in the CLI interface. See Section 7.2.24.

Example 7-21 Monitor Jhuse

 
 JOURNAL USAGE ON NODE NODEA          AT 11:18:19 Wed Jan 02 2002 
 
 LOCAL JOURNAL BLOCKS                 STANDBY JOURNAL(S) BLOCKS 
 
 Maximum                       4992   Maximum                                0 
 Allocated             1984 /  4992   Allocated               0 /            0 
[                40%               ] [                 0%                     ] 
 In use                 928 /  4992   In use                  0 /            0 
[                19%               ] [                 0%                     ] 
 Peak used              928    4992   Peak used               0 /            0 
[                19%               ] [                 0%                     ] 
 
Number of open local journals:    1  Number of open remote journals:         0 
 

7.2.22 Monitor Jnlhtml

In the browser interface, displays the same information as the Monitor Journal command displays in the CLI interface. See Section 7.2.23, Monitor Journal.

7.2.23 Monitor Journal

Displays information about journal usage, including total number of entries and records written, number of records read, and how many bytes were involved. Bar graphs showing current usage of journal blocks (as a percentage of the total) are also provided. The bar graphs appear under the first line of the display JNL_xxx_BLOCKS_IN_USE .

The local journal is the journal on the named node. Standby journals are journals of standby nodes that are being accessed due to restart or catch-up situations. Under normal conditions, standby journal counts are zero.

Example 7-22 Monitor Journal

 
   JOURNAL USAGE ON NODE NODEA            AT 10:36:05 Tue Apr  6 1999 
 
   LOCAL JOURNAL                           STANDBY JOURNAL(S) 
 
   JNL_LCL_BLOCKS_IN_USE       128         JNL_RMT_BLOCKS_IN_USE            0 
   [___             13%          ]         [                0%              ] 
   JNL_LCL_NR_BLOCKS           992         JNL_RMT_NR_BLOCKS              992 
   JNL_LCL_TOP_BLOCKS_USED     128         JNL_RMT_TOP_BLOCKS_USED          0 
   JNL_LCL_BLOCKS_AVAILABLE    864         JNL_RMT_BLOCKS_AVAILABLE         0 
   JNL_LCL_TX_ENTRIES            1         JNL_RMT_TX_ENTRIES               0 
   JNL_LCL_TX_RECORDS            2         JNL_RMT_TX_RECORDS               0 
   JNL_LCL_MEMORY_BYTES     530121         JNL_RMT_MEMORY_BYTES          4197 
   JNL_LCL_DISK_READS           31         JNL_RMT_DISK_READS              33 
   JNL_LCL_BLOCKS_READ         992         JNL_RMT_BLOCKS_READ           1056 
   JNL_LCL_DISK_WRITES          12         JNL_RMT_DISK_WRITES              0 
   JNL_LCL_BLOCKS_WRITTEN       14         JNL_RMT_BLOCKS_WRITTEN           0 
   JNL_LCL_ENTRIES_TOTAL       201         JNL_RMT_ENTRIES_TOTAL            5 
   JNL_LCL_RECORDS_TOTAL       398         JNL_RMT_RECORDS_TOTAL            9 
   JNL_LCL_RECORDS_READ         21         JNL_RMT_RECORDS_READ             0 
   JNL_LCL_REC_BYTES_READ     8006         JNL_RMT_REC_BYTES_READ           0 
   JNL_LCL_NONTX_ENTRIES         5         JNL_RMT_NONTX_ENTRIES            0 
 
   JNL_LCL_OPEN_JOURNALS    2 
    

7.2.24 Monitor Juse

Displays bar graphs of usage for local and remote journals.

Example 7-23 Monitor Juse

 
 JOURNAL USAGE ON NODE NODEA          AT 11:18:19 Wed Jan 02 2002 
 
 LOCAL JOURNAL BLOCKS                 STANDBY JOURNAL(S) BLOCKS 
 
 Maximum                       4992   Maximum                                0 
 Allocated             1984 /  4992   Allocated               0 /            0 
[                40%               ] [                 0%                     ] 
 In use                 928 /  4992   In use                  0 /            0 
[                19%               ] [                 0%                     ] 
 Peak used              928    4992   Peak used               0 /            0 
[                19%               ] [                 0%                     ] 
 
Number of open local journals:    1  Number of open remote journals:         0 
 

7.2.25 Monitor Link

Displays a number of per-link counters. The /LINK= link-name qualifier can be used to display the values for one specific link; otherwise the total values for all links are displayed.

Example 7-24 Monitor Link

LINK COUNTERS  Tue Sep 19 2000 14:24:44, NODE: -ALL- , LINK: -ALL-  -> -ALL- 
 
ncf_protocol             0        nio_writing              0 
ncf_timeout              0        nio_reading              0 
ncf_linkexit             0        nio_wrerror              0 
ncf_disconnect           0        nio_rderror              0 
ncf_thirdparty           0        nio_rdincmp              0 
ncf_pathlost             0        nio_seqerr               0 
ncf_responses_sent       3        nio_bufovf               0 
ncf_queries_rcvd        11        nio_reads_active         3 
ncf_responses_rcvd       2        nio_writes_active        0 
ncf_queries_sent        10        nio_bytes_rcvd    44206961 
ncf_ipt_msgs_rcvd       16        nio_bytes_sent    44206996 
ncf_ipt_msgs_sent       16        nio_pckts_rcvd      412114 
ncf_link_gain            4        nio_pckts_sent      412114 
ncf_link_loss            0        nio_msgs_rcvd       189284 
ncf_aborted              0        nio_tmo_sends       161307 
ncf_rejected             1        nio_tot_stall_sec        0 
ncf_accepted             1        nio_tot_stalls           0 
ncf_confirmed            1        qrm_req_link_queue       0 
ncf_initiated            2        qrm_rsp_link_queue       0 


Previous Next Contents Index