The FLUSH NAME_CACHE command flushes RTR's internal network name cache.

Format

FLUSH NAME_CACHE

Description

The FLUSH NAME_CACHE command removes information for all known nodes from RTR's internal network name cache.

Network links could become unstable if a Distributed Name Service (DNS) was configured improperly or the service was slow in responding. During extreme DNS latency, RTR could timeout the connections to nodes waiting for a DNS response. To avoid these problems, RTR has implemented an internal node-name-to-id cache; this reduces RTR's exposure to degraded name servers. The contents of the cache can then be deleted using the command FLUSH NAME_CACHE.

FLUSH NAME_CACHE can be used if the network has been reconfigured or nodes have changed their addresses.

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 clustering, the /CLUSTER qualifier causes the relevant command to be executed on the local node only.

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

See CREATE JOURNAL; INITIALIZE is only retained for compatibility reasons.

The LOG command directs RTR to write a log message to a log file.

Format

LOG

Description

The LOG command specifies a defined log entry to be written to its log messages. You can write log messages to the operator console and to a maximum of four log files. Log files must be periodically purged to avoid difficulties with full disks. Use SET LOG to specify a new file and delete the old one.

If neither the /OPERATOR nor the /FILE qualifier is specified, logging is suppressed.

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 clustering, the /CLUSTER qualifier causes the relevant command to be executed on the local node only.

/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

• SHOW LOG

Examples

 RTR> LOG/OUTPUT=RTRLOG.LOG "Message check here"
      

This command tells RTR to write a log message to the file RTRLOG.LOG.

 RTR> LOG/CLUSTER="Check for this message to see if 
logging is working"
      

This command tells RTR to write log messages to all members of a cluster.

 RTR> LOG/NODE=hostname "Message check HERE"
      

This command tells RTR to write a defined log message to the log file on the node hostname .

The MODIFY JOURNAL command specifies the desired and maximum allowed sizes of RTR's recovery journal.

Format

MODIFY JOURNAL [disk-1] ... [,disk-n]

Description

The MODIFY JOURNAL command specifies how the size of RTR recovery journal files on the specified disks can be modified. The target or desired size is specified using the /BLOCKS qualifier. The maximum_allowed size is specified using the /MAXIMUM_BLOCKS qualifier. /BLOCKS and /MAXIMUM_BLOCKS are positional qualifiers, so journal files need not be the same size on each disk.

RTR only uses journal files on nodes that are configured to run servers, that is, on backends and on routers with callout servers.

Note that the MODIFY JOURNAL command does not cause immediate journal file extension. Actual file size modifications take place on demand (by the RTRACP) within the limits defined by the MODIFY JOURNAL command.

The MODIFY JOURNAL command assumes that a journal already exists for the node. If a journal does not exist, an error message is output.

In contrast to the CREATE JOURNAL command, the MODIFY JOURNAL command is normally entered interactively, not automatically from a startup command procedure.

Parameters

disk-1 ... disk-n

Specifies a list of disk names where journal files are modified.

Refer to the CREATE JOURNAL command for information about disks used for journal files.

Qualifiers

/BLOCKS[=nr-blocks]

/BLOCKS=1000 (D)

Specifies the size of the journal file in blocks. This qualifier can be applied locally to each disk or globally for all disks.

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

/MAXIMUM_BLOCKS[=nr-blocks]

/MAXIMUM_BLOCKS=1000 (D)

Specifies the maximum size that the journal file can use. This qualifier can be applied locally to each disk or globally for all disks.

/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
• INITIALIZE JOURNAL
• SHOW JOURNAL

Example

 RTR> MODIFY JOURNAL "/dev/rz3a" /BLOCK=2000 /MAXIMUM_BLOCKS=20000
      

This command specifies that the desired size of the journal file is 2000 blocks, and the maximum journal file size is 20,000 blocks.

OpenVMS example

 RTR> MODIFY JOURNAL DISK1$:/BLOCKS=3000/MAXIMUM_BLOCKS=20000
      

This command specifies that the desired size of the journal file is 3000 blocks, and the maximum journal file size is 20,000 blocks.

The MONITOR command displays a monitor picture on the screen.

Format

MONITOR [monitor-filespec]

Description

The MONITOR command allows certain RTR status variables to be continuously displayed on your terminal.

The individual items displayed in the monitor picture can be defined interactively using DISPLAY commands and then executed using a MONITOR/RESUME command.

You can also put the DISPLAY commands into a file (called a monitor file) and then issue a MONITOR monitor-filespec command.

See Chapter 6 for a description of standard monitor pictures.

Parameters

monitor-filespec

Specifies a file containing DISPLAY commands. Monitor file names are of the form monitor-filespec.mon

This file can specify either a user-defined display or one of the standard displays supplied with RTR. If monitor-filespec contains only the file-name portion of a file specification, the RTR utility first searches the platform-specific location for a standard monitor file.

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 clustering, the /CLUSTER qualifier causes the relevant command to be executed on the local node only.

/COUNT=nr-updates

/COUNT=infinite (D)

Specifies how many times the RTR utility updates the screen before exiting or returning to the RTR> prompt.

The default is that RTR updates the screen until CTRL-Z, CTRL-Y or another RTR command is entered. Use the /COUNT qualifier when the /OUTPUT qualifier is being used to redirect output to a file. In this case, nr-updates specifies how many screen images are written to the file.

/FACILITY=facility-name

/NOFACILITY (D)

Specifies the name of the facility to be monitored. This is only meaningful if at least one facility counter is displayed.

/IDENTIFICATION=process-id

/NOIDENTIFICATION (D)

Specifies the hexadecimal process-id of the process to be monitored. This is only meaningful if at least one process counter is to be displayed.

/INTERVAL[=delay-seconds]

/INTERVAL=2 (D)

Specifies how frequently RTR updates the screen. Delay-seconds is the number of seconds that RTR waits after completing one screen update before starting the next. Note that the interval between updates will always be slightly longer than Delay-seconds , depending on the complexity of the display and the number of nodes being monitored.

/LINK=link-name

/NOLINK (D)

Specifies the node name for the link to be monitored. This is only meaningful if at least one link counter is to be displayed.

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

/NOPARTITION (D)

Specifies the names of the partitions to be monitored.

/RESUME

/NORESUME (D)

Re-executes the last MONITOR command. The qualifiers /OUTPUT, /INTERVAL and /COUNT may be used with /RESUME. All other qualifiers are ignored. Use this qualifier to reset all the averages currently being displayed. It is also useful if monitoring is resumed after issuing one or more RTR commands.

/VERIFY

/NOVERIFY (D)

Specifies that the contents of monitor-filespec are echoed on stdout . This is useful when developing monitor files to find the exact location of syntax errors.

Related commands

• SCROLL
• CLEAR
• DISPLAY NUMERIC
• DISPLAY BAR
• DISPLAY TEXT

Examples

 RTR> MONITOR CALLS/NODE=(TR2,TR1)/INTERVAL=10 (1)
 RTR> SHOW PROCESS  (2)
 RTR> MONITOR/RESUME  (3)
      

1. Display the CALLS picture, monitoring nodes TR2 and TR1 every 10 seconds.
2. The SHOW PROCESS command is entered, interrupting the display.
3. Redisplay the CALLS picture using the original parameters.

 RTR> MONITOR TRAFFIC/COUNT=10/OUTPUT=PICTURE.LIS 
      

This command stores 10 images of the TRAFFIC picture in the file PICTURE.LIS .

The QUIT command quits from the RTR prompt.

Format

QUIT

Description

The QUIT command exits from the RTR prompt and returns control to the operating system prompt. The command has no parameters or qualifiers. Same as EXIT.

The RECALL command displays a previously entered command for subsequent command editing.

Format

RECALL [command-specifier]

Description

When you enter commands to the RTR Utility, they are stored in a recall buffer for later use with the RECALL command. Commands can be recalled by either entering the first few characters of the command or the command's number. Use the RECALL/ALL command to list the last 20 commands.

When you recall a command, the RTR Utility displays the command but does not execute it. To execute the command as it appears, press RETURN. You can also use the command editing facility to make changes in the command line and then press RETURN to process the revised version of the command.

Parameters

command-specifier

Specifies either the command number or the first few characters of the command you want to recall.

If command-specifier is omitted, the most recently entered command is recalled.

Qualifiers

/ALL

/NOALL (D)

Displays all the commands (and their numbers) available for recall.

Examples

 RTR> CREATE FACILITY QUOTES/FRONT=FE3/ROUTER=TR2 (1)
 RTR> SHOW FACILITY/LINK  (2)
 RTR> RECALL CREATE  (3)
 RTR> CREATE FACILITY QUOTES/FRONT=FE3/ROUTER=TR2  
 RTR> CREATE FACILITY ORDERS/FRONT=FE3/ROUTER=TR2 (4)
 
      

1. Create facility QUOTES.
2. Check the links.
3. Recall the CREATE FACILITY command.
4. Change the facility name to ORDERS and resubmit the command.

The REGISTER RESOURCE_MANAGER command registers an instance of a resource manager (RM) with RTR.

Format

REGISTER RESOURCE_MANAGER [resource_name]

REGISTER RM [resource_name]

Description

The REGISTER RESOURCE_MANAGER command registers multiple resource managers or instances of resource managers (up to 16) with the current transaction manager. A different resource manager (RM) instance name is needed for each referenced database. Use this command after the RTR ACP is started and before the RTR facilities associated with this resource manager are created. Each RM can be associated with only one facility, but one facililty can be associated with multiple RMs.

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

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

Parameters

resource_name

Specifies the name of the resource to be registered.

Any application program using this resource must specify the same name when it calls rtr_open_channel() .

Resource names can contain up to 30 characters. Letters, numbers and underline characters are all valid, but the first character of a resource name must be a letter.

The default value for resource_name is RTR$DEFAULT_RESOURCE .

Qualifiers

/OPEN_STRING=open_string

RTR uses the OPEN_STRING qualifier to open a connection to the underlying resource manager. Open_string is a null-terminated character string that may contain instance-specific information for the resource manager. The maximum length of the string is 256 bytes (including the null terminator). You must consult the resource manager system administrator to get the appropriate open string.

If this qualifier is not specified, RTR uses a null open string to open the resource manager.

/CLOSE_STRING=close_string

RTR uses the CLOSE_STRING qualifiers to close a connection to a resource manager. Close_string is a null-terminated character string with a maximum length of 256 bytes (including the null terminator). If the resource manager does not require a close string to close the connection to the resource manager, you do not need to use this qualifier. You must consult the resource manager's system administrator documentation to get the appropriate close string.

/LIBRARY_PATH=library_path

Specifies the path and name of the XA library provided by the resource manager. RTR uses the pathname to load the XA library and resolve symbols at runtime.

This qualifier is required.

/XASWITCH_NAME=switch-name

Specifies an XA switch structure name that RTR uses to resolve symbols when it loads an XA library. Each resource manager is required to provide an XA switch and publish the switch structure name so that a transaction manager such as RTR can gain access to the RM's XA routines. You must consult the resource manager's system administrator documentation to get the proper switch name.

This qualifier is required.

Related commands

• UNREGISTER RESOURCE_MANAGER
• SHOW RESOURCE_MANAGER

Examples

RTR> REGISTER RM rmi_1 - _RTR> /open_string="Oracle_XA+Acc=P - _RTR> /user/pw+SesTm=15+db=accounting" - _RTR> /close_string="" /xaswitch_name=xaosw - _RTR> /library_path="library_path"