# hp Reliable Transaction Router
System Manager's Manual

Previous | Contents | Index

# SHOW LOG

> The SHOW LOG command displays the names of the current log files.

## Format

> SHOW LOG

Command Qualifiers | Defaults
--- | ---
/CLUSTER | /NOCLUSTER
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout

## Description

> The SHOW LOG command shows the names of the current RTR log files as defined with the SET LOG command.

## Qualifiers

> ### /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 remote command capability, the /CLUSTER qualifier causes the relevant command to be executed on the local node only. See Section 1.4 for more information.

> ### /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.

### Related commands

- SET LOG

## Example

     RTR> SHOW LOG  (1)

     Messages not being sent to operator console  (2)

     Log file[1]:    /usr/users/someone/rtr_logfile.log   (3)

> 1. Shows where RTR log messages are currently written
> 2. Shows log messages are currently not being sent to the operator log.
> 3. Shows log messages are currently being written to file `rtr_logfile.log` .

# SHOW MODE

> The SHOW MODE command displays the current RTR mode.

## Format

> SHOW MODE

Command Qualifiers | Defaults
--- | ---
/CLUSTER | /NOCLUSTER
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout

## Description

> The SHOW MODE command shows the currently running user group for RTR. For nogroup (system) mode, a null group name is displayed. SET MODE command for further information about modes.

## Qualifiers

> ### /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 remote command capability, the /CLUSTER qualifier causes the relevant command to be executed on the local node only. See Section 1.4 for more information.

> ### /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.

### Related commands

- SET MODE

##

### Examples

     RTR> SHOW MODE

     Group name is "develop"

# SHOW NODE

> The SHOW NODE command shows the node network status, the autoisolation state, the node inactivity timer, the detection interval, and the `request_info cache` lifetime.

## Format

> SHOW NODE

Command Qualifiers | Defaults
--- | ---
/CLUSTER | /NOCLUSTER
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout

## Description

> The SHOW NODE shows the network status, the autoisolation state (enabled or disabled), the node inactivity timer, the detection interval, and the `request_info cache` lifetime.

## Qualifiers

> ### /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 remote command capability, the /CLUSTER qualifier causes the relevant command to be executed on the local node only. See Section 1.4 for more information.

> ### /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.

### Related commands

- SET NODE/ISOLATE
- SET LINK

##

### Examples

     RTR> SHOW NODE  (1)
    Node properties:

    Network state:               enabled (2)
    Auto isolation:             disabled  (3)
    Inactivity timer/s:               60  (4)
    Detection interval/s:             20  (5)
    request_info cache lifetime/s:    20  (6)

> 1. SHOW NODE command
> 2. Shows network status
> 3. Shows auto isolation state (enabled or disabled)
> 4. Shows inactivity timer value in seconds
> 5. Shows detection interval in seconds
> 6. Shows cache lifetime in seconds

# SHOW PARTITION

> The SHOW PARTITION command displays server data partition information.

## Format

> SHOW PARTITION

Command Qualifiers | Defaults
--- | ---
/BACKEND | /NOBACKEND
/BRIEF | /NOBRIEF
/CLUSTER | /NOCLUSTER
/FACILITY[=facility-name] | /FACILITY="*"
/FULL | /NOFULL
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout
/ROUTER | /NOROUTER

## Description

> The SHOW PARTITION command displays information about key range partitions, their states, and current transaction activity. This information is useful for diagnosing bottlenecks or partition difficulties in RTR. For more details, also see Section 2.15.

> The State field of SHOW PARTITION /BACKEND can display the following values:

> Table 8-23 Key-Range or Partition States
> State | Meaning
> --- | ---
> wt_tr_ok | Server is waiting for routers to accept it
> wt_quorum | Server is waiting for backend to be quorate
> lcl_rec | Local recovery
> lcl_rec_fail | Primary server waiting for access to a restart journal
> lcl_rec_icpl | Getting next journal to recover from
> lcl_rec_cpl | Processed all journals for local recovery
> shd_rec | Shadow recovery
> shd_rec_fail | Shadow server waiting for access to a restart journal
> shd_rec_icpl | Shadow getting next journal to recover from
> shd_rec_cpl | Processed all journals for shadow recovery
> catchup | Secondary is catching up with primary
> standby | Server is declared as standby
> active | Server is active
> pri_act | Server is active as primary shadow
> sec_act | Server is active as secondary shadow
> remember | Primary is running without shadow secondary

> The State field of SHOW PARTITION /ROUTER can display the following values:

> Table 8-24 Router Partition States
> State | Meaning
> --- | ---
> BLOCKED | Key range is recovering or awaiting journal access
> ACTIVE | Primary server is ready to accept transactions
> CATCHUP | Secondary server is catching up with primary
> TAKEOVR | Standby take-over is in progress
> LAGGING | Secondary is ready, primary is still recovering

## Qualifiers

> ### /BACKEND

> ### /NOBACKEND (D)

> Displays information about backend partitions; it shows the partition state and low and high bounds. /BACKEND with /FULL provides more detailed information for a partition, giving the current queue depth (transactions active) on a partition. This is useful for determining whether a server is processing transactions correctly.
> - `Last Rcvy BE:` shows from which node recovery information may be fetched.
> - `Txns Rcvrd:` shows the number of transactions actually recovered.

> The default is to output brief router and backend information.

> ### /BRIEF

> ### /NOBRIEF (D)

> Brief output gives a one-line listing of each partition in the system, showing the partition name, the facility in which it resides, and the partition state. Since space on the line is limited, partition names may be truncated to fit.

> ### /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 remote command capability, the /CLUSTER qualifier causes the relevant command to be executed on the local node only. See Section 1.4 for more information.

> ### /FACILITY

> ### /FACILITY="*" (D)

> Specifies the facility name for which information should be displayed.

> By default, information is displayed for all facilities.

> ### /FULL

> ### /NOFULL (D)

> Gives a detailed listing of server partition information.

> The following items are displayed:

> - Key segment low and high bounds
> - Counts of the active and free servers bound to the partition
> - Counts of the active and recovered transactions for the partition
> - The state of transaction presentation - one of active, suspended or suspending
> - The current failover policy - one of `fail_to_standby` , `fail_to_shadow` or `pre_v32_compatibility`

> The SHOW PARTITION command displays callout server data as backend server data because a callout server uses server, not router, data structures. A callout server actually runs on the router identified for its facility.

> ### /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.

> ### /ROUTER

> ### /NOROUTER (D)

> Displays information about router partitions; it shows the partition state and partition low and high bounds. It can be used to quickly determine the current primary node for a given partition. Using /ROUTER with /FULL provides more detailed information, such as the main, shadow and standby servers for the partitions, as seen from the router.

> Partition bounds are shown as ASCII characters if there is a translation, otherwise as hexadecimal digits. Only the least significant 4 bytes are shown.

##

### Examples

> The following example shows the /FULL output of the SHOW PARTITION command in a shadow configuration.

>     RTR> SHOW PARTITION/FULL

>     Router partitions on node mspl01 in group "rtrlkg" at Tue Oct 15 13:40:53 2002

>     Backend partitions on node mspl01 in group "rtrlkg" at Tue Oct 15 13:40:53 2002

>     Partition name:                                                   Partition_A

>     Configuration:-

>     Facility:                SHADOW_TEST     State:                       pri_act(1)
>     Low bound:                       "A"     High bound:                      "A"
>     Active servers:                    0     Free servers:                      1(2)
>     Transaction presentation:     active(3)   Last Rcvy BE:                 mswe01(4)
>     Active transaction count:          0(5)   Transactions recovered:        0
>     Failover policy:     fail_to_standby     Key range ID:               16777216
>     Master router:                 (nil)(6)   Relative priority:                 2(7)
>     Recovery Retry Count:              0(8)   Resource Manager:

>     Features:                                         Shadow,NoStandby,Concurrent(9)

>     Partition name:                                                   Partition_B

>     Configuration:-

>     Facility:                SHADOW_TEST     State:                       sec_act
>     Low bound:                       "B"     High bound:                      "B"
>     Active servers:                    0     Free servers:                      1
>     Transaction presentation:     active     Last Rcvy BE:                 mswe01
>     Active transaction count:          0     Transactions recovered:            0
>     Failover policy:     fail_to_standby     Key range ID:               16777217
>     Master router:                 (nil)     Relative priority:                 2
>     Recovery Retry Count:              0     Resource Manager:
>     Features:                                         Shadow,NoStandby,Concurrent

> 1. Partition state, see Section 2.15.
> 2. Number of servers available for processing.
> 3. State of transaction processing.
> 4. Node from which recovery information can be obtained.
> 5. Number of transactions currently active.
> 6. Nodename of master router, if any.
> 7. Priority established with the SET PARTITION command.
> 8. Number of retries for recovery in this partition.
> 9. Features currently set for the given parition.

# SHOW PROCESS

> The SHOW PROCESS command displays information about processes that use RTR.

## Format

> SHOW PROCESS

Command Qualifiers | Defaults
--- | ---
/CLUSTER | /NOCLUSTER
/COUNTER[=counter-name] | /NOCOUNTER
/FULL | /NOFULL
/IDENTIFICATION=process-id | /NOIDENTIFICATION
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout

## Description

> The SHOW PROCESS command displays information about the processes using RTR.

## Qualifiers

> ### /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 remote command capability, the /CLUSTER qualifier causes the relevant command to be executed on the local node only. See Section 1.4 for more information.

> ### /COUNTER[=counter-name]

> ### /NOCOUNTER (D)

> Specifies that the process counters are also to be displayed. `counter-name` is the name of the counter to be displayed. If `counter-name` is omitted, all counters will be displayed. `counter-name` may contain wild card characters.

> ### /IDENTIFICATION=process-id

> ### /NOIDENTIFICATION (D)

> Specifies the process about which information is required. The default (/NOIDENTIFICATION) displays all processes using RTR.

> ### /FULL

> ### /NOFULL (D)

> Equivalent to specifying /COUNTER.

> ### /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.

##

### Examples

>     RTR> SHOW PROCESS
>     Processes:

>     Process-id   Process Name
>     326

# SHOW REQUESTER

> See SHOW CLIENT. The SHOW REQUESTER command has been replaced by SHOW CLIENT and is retained for compatibility reasons only.

# SHOW RESOURCE_MANAGER (SHOW RM)

> The SHOW RESOURCE_MANAGER command displays resource manager (RM) instance information.

> This command is available only on UNIX and Windows NT systems.

## Format

> SHOW RESOURCE_MANAGER [resource_name]

> SHOW RM [resource_name]

Command Qualifiers | Defaults
--- | ---
/CLUSTER | /NOCLUSTER
/FULL | /NOFULL
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout

## Description

> The SHOW RESOURCE_MANAGER command displays information for registered RMs. This command shows information for one or more RMs registered with the current TM.

> Note This command is available only on UNIX and Windows NT systems.

> Refer to Appendix C, RTR XA Support for support information about XA.

## Parameters

> ### resource_name

> Specifies the name of the resource manager instance you want to display. `resource_name` may contain wildcards (* and %), in which case all matching resources are displayed. If `resource_name` is omitted, all configured resources are displayed.

## Qualifiers

> ### /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 remote command capability, the /CLUSTER qualifier causes the relevant command to be executed on the local node only. See Section 1.4 for more information.

> ### /FULL

> ### /NOFULL (D)

> Displays additional information for facilities that reference a particular RM. If no `rmi_name` is included, displays information for all RMs.

> ### /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.

### Related commands

- REGISTER RESOURCE_MANAGER
- UNREGISTER RESOURCE_MANAGER

##

### Examples

     RTR> SHOW RM rmi_0 /full
          Resource Manager:
          RMI Name                : rm_0
          RMID                    : 0
          XA Switch               : msqlsrvxal
          Library path            : .\xadll.dll
          The facility associated with this RM: xatest

Previous | Next | Contents | Index