This command deletes any existing journal files and then creates new ones on DISK1$ and DISK2$. The target sizes of the journal files are 1000 and 2000 blocks, and the maximum sizes are 10,000 and 200,000 blocks respectively.

RTR> CREATE JOURNAL "/dev/rz3a", "/dev/rz2c" /BLOCK=1000 /MAXIMUM_BLOCK=2000

This command creates journal files on /dev/rz3a and /dev/rz2c . The target sizes of the journal files is 1000 blocks and the maximum size of the journal on /dev/rz2c is 2000 blocks.

The CREATE PARTITION command creates an RTR partition.

Format

CREATE PARTITION partition_name

Description

The CREATE PARTITION command defines an RTR partition. The partition characteristics that may be defined include key range or ranges and whether attached server processes can be shadows or standbys.

The command must be issued before any server application programs using the partition are started.

Parameters

partition_name

Specifies the name of the partition to be created. Partition names must be unique within a facility.

Any application program which uses this partition must specify the same name when it calls rtr_open_channel() .

Partition names can contain up to 63 characters. Letters, numbers and underline characters are all valid. The first character of a partition name can be a letter or a number.

If a partition name already exists in the facility, the command fails.

There is no default value for partition_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 clustering, the /CLUSTER qualifier causes the relevant command to be executed on the local node only.

/CONCURRENT (D)

/NOCONCURRENT

Specifies that concurrent servers are allowed for this partition.

/FACILITY

Specifies the name of the facility in which the partition is being created.

/KEYn=keysegdesc

Specifies a partition key segment. Up to 9 key segments may be defined for a partition (KEY1, KEY2,... up to KEY9). If more than 9 key segments are required, a named partition can be created using the rtr_open_channel() call.

The syntax of the KEYn qualifier is:

/KEYn= (type_of_key=[signed|unsigned|string], - length_of_key=nnnn, - offset_of_key=nnnn, - low_bound=[string|nnnn] - high_bound=[string|nnnn]

type_of_key= Specifies the field type of the key. The key-type must be one of unsigned , signed or string . The default is unsigned .

length_of_key=nnnn Specifies the length of the key field in enqueued messages in bytes. For signed or unsigned ints, length may be either 1, 2, 4 or 8 bytes. The default value for key-length is 4 bytes.

offset_of_key=nnnn Specifies the offset of the key within the messages in bytes. The default is zero, that is, the key is at the start of the messages.

low_bound= Specifies the lower bound of the key range that servers in the partition will service. The interpretation of low-bound depends on the key type; if the key is of type string, it is interpreted as text, otherwise it is interpreted as a numeric value. The default for low-bound is the smallest possible value that can fit in the specified key type.

If the key bound value length is less than the key length (given in length_of_key ), the key bound will automatically be null-padded to the required length.

high_bound= Specifies the upper bound of the key range that servers in the partition will service. The interpretation of high-bound depends on the key type. If the key is of type string, it is interpreted as text, otherwise it is interpreted as a numeric value. The default for high-bound is the largest possible value that can fit in the specified key type.

If the key bound value length is less than the key length (given in length_of_key ), the key bound will automatically be null-padded to the required length.

If the specified key range overlaps that of an existing partition in the facility, or if the key segment description conflicts with an existing definition, the command fails.

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

/RESOURCE_MANAGER

Specifies that the partition will be managed by an underlying resource manager, rmname , via the XA protocol.

When you specify the XA-managed attribute for a partition at the command line, the attribute remains until the partition goes away. A partition can be managed by only one resource manager. When creating a new partition, do not use an existing resource manager name unless the partition previously using the resource manager name has been deleted.

/SHADOW

/NOSHADOW (D)

Specifies that shadow servers are allowed for this partition.

/STANDBY (D)

/NOSTANDBY

Specifies that standby servers are allowed for this partition.

Related commands

• CREATE FACILITY
• SET PARTITION

The DEFINE /KEY command assigns a string to a keyboard function key.

Format

DEFINE /KEY key-name "equivalence-string"

Description

This command lets you assign a string to a function key, possibly overriding any predefined function that was bound to that key. When you then press the key, the RTR Utility enters the currently associated string into your command line. The RTR DEFINE /KEY command is similar to the OpenVMS DCL DEFINE /KEY command.

A key definition remains in effect until you redefine the key or exit from the RTR Utility. You can include key definitions in command procedures, for example in the RTR Utility initialization file.

The /IF_STATE qualifier lets you increase the number of key definitions available on your terminal. The same key can be assigned any number as long as each definition is associated with a different state.

By default, the current key state is the DEFAULT state. The current state can be changed by pressing a key that causes a state change (that is, a key that was defined with the DEFINE /KEY /STATE command).

Parameters

key-name

Specifies a function key to be assigned a string. Table 7-18 describes the valid key names.

Table 7-18 Key Names

Key-name	LK201	VT100-type
PF1	PF1	PF1
PF2	PF2	PF2
PF3	PF3	PF3
PF4	PF4	PF4
KP0, KP1 ..KP9	Keypad 0 .. 9	Keypad 0 .. 9
PERIOD	Keypad period (.)	Keypad period (.)
COMMA	Keypad comma (,)	Keypad comma (,)
MINUS	Keypad minus (-)	Keypad minus (-)
ENTER	ENTER	ENTER
E1	Find
E2	Insert Here
E3	Remove
E4	Select
E5	Prev Screen
E6	Next Screen
HELP	Help
DO	Do
F6, F7, .. F20	F6, F7, .. F20

equivalence-string

Specifies the string to be processed when the specified key is pressed. Typically, this is all or part of an RTR command.

If the string contains spaces or non-alphanumeric characters, it must be enclosed in quotation marks.

Qualifiers

/ECHO (D)

/NOECHO

Controls whether the command line is displayed after the key has been pressed. Do not use /ECHO with /NOTERMINATE.

/IF_STATE=state-name

/NOIF_STATE (D)

Specifies the name of a state to which a key definition applies. /IF_STATE assigns the key definitions to the specified states. A state name can be any appropriate alphanumeric string. /NOIF_STATE (the default) assigns the key definition to the DEFAULT state.

/LOCK_STATE

/NOLOCK_STATE (D)

Controls how long the state set by /SET_STATE remains in effect after the specified key is pressed. /LOCK_STATE causes the state to remain in effect until it is changed explicitly by another function key being pressed that has the /SET_STATE attribute. /NOLOCK_STATE (the default) causes the state to remain in effect only until the next terminator character is typed, or until the next define function key is pressed.

/LOG

/NOLOG (D)

Controls whether a message is displayed indicating that the key definition has been successfully created.

/SET_STATE=state-name

/NOSETSTATE (D)

Controls whether pressing the key changes the current key state. /SET_STATE changes the current state to state-name when you press the key. /NOSET_STATE (the default) causes the current state to remain in effect.

/TERMINATE

/NOTERMINATE (D)

Controls whether the specified string is to be terminated (processed) when the key is pressed. /TERMINATE causes the string to be terminated when the key is pressed. /NOTERMINATE (the default) allows you to press other keys before terminating the string by pressing the [RETURN] key.

Related commands

• SHOW KEY

Examples

 RTR> DEFINE /KEY PF3 "SHOW RTR" /TERMINATE
 DEFAULT PF3 key has been defined as "SHOW RTR"
 RTR> [PF3]
 
 RTR running on node BE1
 
      

The DEFINE /KEY command defines the [PF3] key on the keypad to perform a SHOW RTR command. DEFAULT refers to the default state.

 RTR> DEFINE /KEY PF1 "HELP " /SET_STATE=GOLD /NOTERMINATE /ECHO
 DEFAULT PF1 key has been defined as "HELP "
 RTR> DEFINE /KEY PF1 " CREATE" /TERMINATE /IF_STATE=GOLD /ECHO
 GOLD PF1 key has been defined as "CREATE"
 RTR> [PF1]
 RTR> HELP [PF1]
 RTR> HELP CREATE
 The "CREATE FACILITY" command is used to ...
      

The first DEFINE /KEY command defines the [PF1] key to be the string HELP. The state is set to GOLD for the subsequent key. The /NOTERMINATE qualifier instructs the system to remain in command input mode when the key is pressed. The second DEFINE /KEY command defines the use of the [PF1] key when the keypad is in the GOLD state. When the keypad is in the GOLD state, pressing [PF1] will cause the current read to be terminated.

If you press [PF1] twice, the system displays and processes the HELP CREATE command.

The word DEFAULT in the second line of the example refers to the fact that [PF1] has been defined in the default state. Note the space before the word CREATE in the second DEFINE /KEY command. If the space is omitted, the system fails to recognize CREATE as the keyword for the HELP command.

The DELETE FACILITY command deletes an RTR facility.

Format

DELETE FACILITY facility_name

Description

The DELETE FACILITY command removes the specified facility on the node where the command is issued. After issuing this command applications are able to use the facility. Any outstanding transactions using the facility are aborted.

Parameters

facility_name

The name of the facility to delete.

The parameter facility_name must be supplied.

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

• CREATE FACILITY
• SHOW FACILITY

Examples

See Chapter 2, Starting and Setting Up RTR, for examples of how to use the DELETE FACILITY command.

The DELETE JOURNAL command deletes an RTR journal.

Format

DELETE JOURNAL

Description

The DELETE JOURNAL command deletes a previously created RTR journal on the node where the command is issued.

The DELETE JOURNAL command will fail if a journal does not exist, or if a journal has been created but is currently in use. The command causes the previous contents of the journal, if any, to be destroyed.

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

• CREATE JOURNAL
• MODIFY JOURNAL
• SHOW JOURNAL

The DELETE PARTITION command deletes an RTR PARTITION.

Format

DELETE PARTITION partition_name

Description

The DELETE PARTITION command removes the specified partition on the node where the command is issued.

Parameters

PARTITION_name

The name of the partition to delete.

The parameter partition_name must be supplied. It may be specified as partition_name or as facility_name:partition_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 clustering, the /CLUSTER qualifier causes the relevant command to be executed on the local node only.

/FACILITY

Specifies the name of the facility from which the partition is being deleted.

/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 PARTITION
• SHOW PARTITION