Reliable Transaction Router
System Manager's Manual


Previous Contents Index

Value of new_state may be one of the following:

ABORT
COMMIT
DONE
EXCEPTION

Note that one cannot always change a transaction's state from one legitimate transaction state to another. Some state changes are not valid. The following table shows state changes that are valid.

Table 7-19 Valid Transaction State Changes
    NEW STATE  
Current State COMMIT ABORT EXCEPTION DONE
SENDING   YES    
VOTED YES YES    
COMMIT     YES YES
EXCEPTION YES     YES
PRI_DONE       YES

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

/PARTITION

/PARTITION=partition_name

Specifies the name of a partition within which all transactions are running. A partition name must be supplied.

Use SHOW PARTITION to view the names of the currently active partitions.

/SINCE[=date]

Selects only those transactions whose timestamp is after the specified date. Default is the current date.

/STATE=current_state

Selects a particular transaction or a set of transactions that are in the specified current_state transaction state. This qualifier is required and the current_state value must be specified.

Value of current_state may be one of the following:

SENDING
VOTED
COMMIT
EXCEPTION
PRI_DONE

Use the SHOW TRANSACTION command to help you find what is the current state of a particular transaction.

/USER[=user-id]

/USER=all users (D)

Allows you to select transactions that were initiated by a client process.

If /USER is not specified, transactions for all users are affected.

Related commands


Examples


 RTR> SET TRANSACTION "50d01f10,0,0,0,0,2166,522b2001" -
 _RTR> /NEW=ABORT /STATE=SENDING /PART=DB_PART
      

Abort this specified transaction running in the DB_PART partition.


 RTR> SET TRANSACTION /NEW=ABORT /STATE=VOTED /PART=DB_PART
      

Abort all transactions that are in VOTED transaction state and are running in DB_PART partition, in the RTR$DEFAULT-FACILITY facility.

For more examples, refer to Chapter 4, Transaction Management.


SHOW CHANNEL

The SHOW CHANNEL command shows the names and state of channels that have been opened using the CLI API.

Format

SHOW CHANNEL [channel-name]

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

Description

The SHOW CHANNEL command shows the channel type (client or server), the channel name and owner process-id for channels opened using the CLI API.

Parameters

channel-name

Specifies the name of the channel to be displayed. channel-name can contain wildcards. If channel-name is omitted, all declared channels for this window (terminal or virtual terminal) are displayed.

Qualifiers

/ALL_WINDOWS

/NOALL_WINDOWS

Specifies that channels opened in all windows (terminals or virtual terminals) are shown.

/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


Examples


 RTR> SHOW CHANNEL/ALL_WINDOWS  (1)
  
 Channel type Channel name                (Owner pid)   
 server         RTR$DEFAULT_CHANNEL             (28879)  (2)
 client         CLI_CHN                         (28879)  (3)
 client         CLI_CHN2                        (26225)  (4)
 
      

  1. Displays information about all declared channels.
  2. The channel called RTR$DEFAULT_CHANNEL is open as a server channel.
  3. The channel called CLI_CHN is open as a client channel.
  4. The channel called CLI_CHN2 is open as a client channel, and has been opened by another process (in another window).

SHOW CLIENT

The SHOW CLIENT command displays information about client channels.

Format

SHOW CLIENT

Command Qualifiers Defaults
/CLUSTER /NOCLUSTER
/FACILITY[=facility_name] /FACILITY="*"
/FULL None
/IDENTIFICATION=process-id /NOIDENTIFICATION
/NODE[=node-list] /NODE=default-node
/OUTPUT[=filespec] /OUTPUT=stdout

Description

The SHOW CLIENT command displays information about client channels.

Information such as PID, key range, state, event mask and event name 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.

/FACILITY

/FACILITY="*" (D)

Specifies the facility name for which information should be displayed.

By default, information is displayed for all facilities.

/FULL

none (D)

Specifies a detailed listing of client information.

/IDENTIFICATION=process-id

/NOIDENTIFICATION (D)

Specifies the PID of the process for which information is displayed. The default (/NOIDENTIFICATION) displays information for all clients.

/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 CLIENT/FULL  (1)
  
 Process-id:      9234          Facility:       TEST43  (2)
 Channel:         500           Flags:             CLI  (3)
 State:           declared      rcpnam:       "V3TEST" (4)
 User Events:     255           RTR Events:          0 (5)
  
 
      

  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.

Format

SHOW DISPLAY

Command Qualifiers Defaults
/ALL /NOALL
/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

/NOALL (D)

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


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


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. 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.7, Router Load Balancing 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:

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

/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


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.


Previous Next Contents Index