# hp Reliable Transaction Router
System Manager's Manual

Previous | Contents | Index

1. Shows the client in detail.
2. Client's process ID and facility name.
3. Client's channel ID and the flags set when the channel was opened.
4. Channel state and recipient name for events.
5. User events and RTR events subscribed to.

# SHOW DISPLAY

> The SHOW DISPLAY command shows which items were displayed by the most recently issued MONITOR command or DISPLAY commands.

> Note This command is not available in the RTR web browser interface.

## Format

> SHOW DISPLAY

Command Qualifiers | Defaults
--- | ---
/ALL | /ALL
/OUTPUT[=filespec] | /OUTPUT=stdout
/X[=column] | Column of previous item
/Y[=row] | Next free row

## Description

> The SHOW DISPLAY command shows which items were displayed by the most recently issued MONITOR command. These may have been read in from a display file using the MONITOR `filespec` command, or entered interactively using DISPLAY commands.

> The item definitions are shown in DISPLAY command format. Use the command SHOW DISPLAY/OUTPUT= `filespec` to create new monitor files.

## Qualifiers

> ### /ALL (D)

> ### /NOALL

> Specifies that all monitored items are shown.

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

> ### /X=column /Y=row

> Specifies that the single item in position ( `column` , `row` ) is shown.

### Related commands

- MONITOR
- DISPLAY NUMERIC
- DISPLAY BAR
- DISPLAY TEXT

##

### Examples

     RTR> MON CALLS  (1)
     RTR> SHOW DISPLAY/ALL  (2)

     DISPLAY TEXT  "RTR api calls, Node: $node_name ,- (3)
              PID: $process_id, Process name: -ALL-" -
             /X=1   /Y=1 -
             /BOLD="1"
        .
        .
        .
     DISPLAY NUMERIC         "rtr_open_channel_succ" -
             /X=1   /Y=5 -
             /BLANK -
             /LABEL=" rtr_open_channel    " -
             /WIDTH=9
        .
        .
        .

> 1. Displays the CALLS monitor picture.
> 2. Shows all the items contained in the monitor picture.
> 3. Displays items in DISPLAY command format. See the relevant DISPLAY commands for a description of the various qualifiers.
> See Section A.1, Interactive Definition of a Monitor Picture, for an example of how to use the SHOW DISPLAY command.

# SHOW ENVIRONMENT

> The SHOW ENVIRONMENT command shows the default nodes used for remote command execution.

## Format

> SHOW ENVIRONMENT

## Description

> The SHOW ENVIRONMENT command shows which nodes are used by default for remote command execution.

### Related commands

- SET ENVIRONMENT

##

### Examples

     RTR> SET ENVIRONMENT/NODE=(FE2,FE3)  (1)
     RTR> SHOW ENVIRONMENT  (2)
     %RTR-S-COMARESEN, commands sent by default to node FE2 (3)
     %RTR-S-COMARESEN, commands sent by default to node FE3

> 1. Sets the command environment so that subsequent commands will be executed on nodes FE2 and FE3.
> 2. Shows which nodes are selected.
> 3. Displays the RTR-S-COMARESEN message for each selected node.

# SHOW FACILITY

> The SHOW FACILITY command shows the names, configuration, and status of one or more facilities.

## Format

> SHOW FACILITY [facility-name]

Command Qualifiers | Defaults
--- | ---
/BALANCE | /NOBALANCE
/CLUSTER | /NOCLUSTER
/CONFIGURATION | /NOCONFIGURATION
/COUNTER[=counter-name] | /NOCOUNTER
/FULL | /NOFULL
/LINKS/BRIEF | /NOLINKS/NOBRIEF
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout
/STATE | /NOSTATE

## Description

> The SHOW FACILITY command shows the names, configuration and status of facilities on the node where the command is executed. If no qualifiers are used, only the facility name or names and the roles in the facility on the node are displayed.

## Parameters

> ### facility-name

> Specifies the name of the facility you want to display. `Facility-name` may contain wildcards (* and %), in which case all matching facilities will be displayed. UNIX users can also employ the ? single-character wildcard. If `facility-name` is omitted, all configured facilities are displayed.

## Qualifiers

> ### /BALANCE

> ### /NOBALANCE (D)

> Specifies that the load balancing status of the facility is also displayed. See Section 2.8, Router Load Balancing and Flow Control for details of load balancing.

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

> ### /CONFIGURATION

> ### /NOCONFIGURATION (D)

> Specifies that the facility configuration is to be displayed. The configuration information indicates the role of the node where the command is executed, and whether:
> - Router callout servers or backend callout servers have been configured
> - Load balancing has been configured
> - Quorum check is being handled on this node
> - Reply consistency check for replayed messages is enabled

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

> ### /NOCOUNTER (D)

> Specifies that the facility counters are displayed. `Counter-name` is the name of the counter. If `counter-name` is omitted, all counters are displayed. `Counter-name` may contain wildcard characters.

> ### /FULL

> ### /NOFULL (D)

> Equivalent to specifying `/CONFIGURATION` , `/STATE` and `/LINK` .

> ### /LINKS

> ### /NOLINKS (D)

> Lists all links to connected nodes in the facility (including the node where the command is executed).

> If the /BRIEF qualifier is used, SHOW FACILITY/LINKS/BRIEF, the facility name is displayed, followed by one or more lines showing the name of each link followed by the link's roles and their status in parentheses.

>     RTR> SHOW FACILITY/LINKS/BRIEF

>     Facilities on node NODEA at Wed Nov 03 11:115:47 1999

>     BOVRIL (Backend coordinator, Router quorate, Frontend connected>

> Backend nodes can be either connected, quorate, or coordinator. Router nodes can be either connected, quorate, or current (current is only seen from a frontend).

> If the /BRIEF qualifier is not used, the following information is shown for each link:

> - Whether the node on this link is active as frontend, router or backend roles.
> - What kind link is active, that is:
>   - frontend to router
>   - router to frontend
>   - router to backend
>   - backend to router
> - Whether the router and backend roles are quorate
> - Whether the router role is the current router for the frontend
> - Whether the backend role is acting as a load balancing coordinator

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

> ### /STATE

> ### /NOSTATE(D)

> Specifies that the state of the facility is displayed.

> On nodes having a backend or router role, the quorum status is shown. Also, the current quorum threshold is shown (default quorum value is shown as zero), and the minimum broadcast rate (if it has been set).

> On a frontend, this qualifier can be used to find out whether the node is currently connected to a router.

### Related commands

- CREATE FACILITY
- DELETE FACILITY
- SHOW LINK

##

### Examples

     RTR> SHOW FACILITY/FULL/NODE=BRONZE  (1)

    Facility:       FUNDS_TRANSFER  (2)
    Configuration:-                 (3)

    Frontend:         no    Router:              yes  Backend:            yes
                            Router call-out:      no  Backend call-out:    no
                            Load balance:         no  Quorum-check off:    no

    State:-                         (4)

    FE -> TR:      unused   Router quorate:      yes  Backend quorate:    yes
                            Quorum threshold:      0  Min broadcast rate:   0

    Links:-                         (5)

    Link to:                      bronze
    Frontend:          no   Router:              yes  Backend:            yes
    Router -> Frontend:no   Frontend -> Router:   no
                            Backend -> Router:   yes  Router -> Backend:  yes
                            Router quorate:      yes  Backend quorate:    yes
                            Router current:       no  Backend coordinator:yes

    Link to:                      airola    (6)
    Frontend:          yes  Router:               no  Backend:             no
    Router -> Frontend:yes  Frontend -> Router:   no
                            Backend -> Router:    no  Router -> Backend:   no
                            Router quorate:       no  Backend quorate:     no
                            Router current:       no  Backend coordinator: no

> 1. Shows all facilities in detail.
> 2. Facility's name.
> 3. Facility's configured roles on this node. In this example, the node is a router and a backend; load balancing, router callouts and backend callouts are not enabled.
> 4. Facility's state. The router and backend roles are quorate. (Quorate means that this node's view of the availability of the other nodes in the configuration matches that of the other backends and routers. A facility that is not in the quorate state is effectively unusable.) The quorum threshold is at the default (zero) and no minimum broadcast rate has been set.
> 5. Facility's links. The first link shown (to node bronze i.e. itself) shows that it is a router, connected to the backend, and the router is quorate. The router is not current because there is no frontend on this connection. The link is also a backend, connected to the router, and this backend is quorate. This backend would also be the backend coordinator if load balancing was enabled.
> 6. Second link shown (to node airola) shows that it is a frontend, and is a frontend to router connection.

    RTR> SHOW FACILITY/BALANCE
    Facilities:

    Facility:       RTR$DEFAULT_FACILITY

    Load:-

    Frontends connected:               1     Frontends allowed:                 1
    Load coordinator:                yes     Quorate routers:                   1
    Total Frontends:                   1     Current Credit:                    1
    FE -> TR:                          -

> This display shows the load balancing status. This node is the current load coordinator.

# SHOW JOURNAL

> The SHOW JOURNAL command displays information about current RTR journal files.

## Format

> SHOW JOURNAL

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

## Description

> The SHOW JOURNAL command shows the disks where the RTR journal files reside, and (optionally) the maximum and allocated number of blocks for each journal file and the journal file name.

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

> ### /FILENAMES

> ### /NOFILENAMES (D)

> /FILE adds the journal file names to the display.

> ### /FULL

> ### /NOFULL (D)

> /FULL adds to the display the maximum and allocated number of blocks for each journal file.

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

- CREATE JOURNAL
- DELETE JOURNAL
- INITIALIZE JOURNAL
- MONITOR JOURNAL
- MONITOR RECOVERY

##

### Examples

     RTR> SHOW JOURNAL/FULL/FILENAMES  (1)

     RTR journal:-
         (2)          (3)            (4)        (5)          (6)
     Disk(1):  /dev/rz3a      Blocks: 1500 Allocated: 1502 Maximum: 3000
     File(1):  /dev/rz3a /rtrjnl/SYSTEM/BRONZE.J01(7)
     Disk(2):  /dev/rz2c      Blocks: 1500 Allocated: 1502 Maximum: 3000
     File(2):  /dev/rz2c /usr/users/rtrjnl/SYSTEM/BRONZE.J11

> 1. Shows the disks used for RTR's recovery journal and the file names
> 2. Shows two disks are currently in use
> 3. Shows device name
> 4. Shows file size in blocks
> 5. Shows allocated file size in blocks
> 6. Shows maximum file size in blocks
> 7. Filename

# SHOW KEY

> The SHOW KEY command displays the key definitions created by the DEFINE /KEY command.

## Format

> SHOW KEY [key-name]

Command Qualifiers | Defaults
--- | ---
/ALL | /NOALL
/FULL | /NOFULL
/OUTPUT[=filespec] | /OUTPUT=stdout
/IF_STATE | /NOIF_STATE

## Description

> The SHOW KEY command shows the key definitions created by the DEFINE /KEY command.

## Parameters

> ### key-name

> Specifies the name of the key whose definition you want displayed. See the description of the DEFINE /KEY command for a list of the valid key names.

## Qualifiers

> ### /ALL

> ### /NOALL (D)

> Requests that all key definitions in the current state be displayed. You can use the /IF_STATE qualifier to request key definitions in other states. Do not specify a key name with the /ALL qualifier. If no state is specified, all key definitions in the current state are displayed.

> ### /FULL

> ### /NOFULL (D)

> Requests that all qualifiers associated with a definition are displayed. By default, only the state of the definition and the definition itself are displayed.

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

> ### /IF_STATE=state-name

> ### /NOIF_STATE (D)

> Specifies the name of a state for which the specified key definitions are displayed. State names can be any appropriate alphanumeric string. State names are created with the DEFINE /KEY command. If you omit the /IF_STATE qualifier or use /NOIF_STATE, key definitions in the current state are displayed.

### Related commands

- DEFINE /KEY

##

### Examples

     RTR> SHOW KEY/FULL
     DEFAULT PF1 defined as ""
     DEFAULT KP0 defined as "MONITOR/RESUME"
     DEFAULT KP2 defined as "SCROLL DOWN 1"
     DEFAULT KP4 defined as "SCROLL LEFT 1"
     DEFAULT KP5 defined as "SCROLL HOME"
     DEFAULT KP6 defined as "SCROLL RIGHT 1"
     DEFAULT KP8 defined as "SCROLL UP 1"
     GOLD KP2 defined as "SCROLL DOWN 10"
     GOLD KP4 defined as "SCROLL LEFT 10"
     GOLD KP6 defined as "SCROLL RIGHT 10"
     GOLD KP8 defined as "SCROLL UP 10"

# SHOW LINK

> The SHOW LINK command displays the configuration and status of the links to other nodes.

## Format

> SHOW LINK [node-name]

Command Qualifiers | Defaults
--- | ---
/CLUSTER | /NOCLUSTER
/COUNTER[=counter-name] | /NOCOUNTER
/FACILITY | /NOFACILITY
/FULL | /NOFULL
/NODE[=node-list] | /NODE=default-node
/OUTPUT[=filespec] | /OUTPUT=stdout
/STATE | /NOSTATE

## Description

> The SHOW LINK command shows the configuration and status of the links to RTR nodes. If no qualifiers are given, a brief display of the links is shown.

## Parameters

> ### node-name

> Specifies the name of a node; the parameters for the link to this node are displayed. `Node-name` may contain wildcards (* and %), in which case all matching links are displayed. If `node-name` is omitted, all known links 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.

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

> ### /NOCOUNTER (D)

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

> ### /FACILITY

> ### /NOFACILITY (D)

> Specifies that the names of facilities using the link are also displayed.

> ### /FULL

> Equivalent to specifying /FACILITY/STATE.

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

> ### /STATE

> ### /NOSTATE (D)

> Specifies that a detailed status of the specified link is displayed.

### Related commands

- SET LINK
- CREATE FACILITY
- SHOW FACILITY/LINK

## Example

>     RTR> SHOW LINK/FULL IRON
>     Links:

>     To Node:                        iron     Address:            iron.zuo.dec.com

>     Status:-

>     Outgoing message sequence nr:     22     Incoming message sequence nr:     22
>     Current receive buffer size:    2048     Current transmit buffer size:   2048
>     Current number of link users:      1     Write buffer timed out:           no
>     Write buffer full, may be sent:   no     Write buffer allocated:          yes
>     I/O error detected in write:      no     I/O error detected in read:       no
>     Pipe temporarily blocked:         no     Connection broken:                no
>     Write issued, not completed:      no     Read is pending:                 yes
>     Node initiated the connection:   yes     Connection established:          yes
>     Connection in progress:           no     Node is configured:              yes
>     Link is in disabled state:        no     Link may be suspect:              no

>     Facilities:-

>     In facility:                  steve2
>     Frontend:             no   Router:              yes   Backend:            no
>     Router -> Frontend:   no   Frontend -> Router:  yes
>     Backend -> Router:    no   Router -> Backend:   no
>                                Router quorate:       no   Backend quorate:    no
>                                Router current:      yes   Backend coordinator:no

> This example shows the:

> - Name and network address of the partner node.
> - Link status.
> - Name of facility using this link and how the link is used in the facility.

Previous | Next | Contents | Index