RDF/IMP and IMPX System Management Manual (RDF 1.3+)

Entering RDFCOM Commands
Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001
8-69
Command Overview
RDFVOLUME $volume
specifies which disk volume on the backup system is to be used for the receiver’s
master image trail (the image trail to which the receiver writes all commit/abort
records). The default is $SYSTEM.
Note that this attribute applies only to the master receiver (the receiver process
configured with an ATINDEX value of 0).
For best performance, do not use $SYSTEM as the RDFVOLUME and do not use
the RDFVOLUME for updater image trails.
If the backup system will run with updating disabled, be sure to specify an
RDFVOLUME disk that has an adequate amount of available space.
If the RDFVOLUME disk becomes filled, the receiver process will receive error
43 messages (Unable to obtain disk space for extent) from the file system until the
situation is corrected.
PRIORITY priority
identifies the execution priority for the receiver process; priority is the execution
priority, from 10 through 199. The default is 165.
PROCESS process-name
specifies the process name for the receiver process; process-name is any unique,
valid process name of up to 5 characters; the first character must be a dollar sign ($).
You cannot specify reserved process names of the form $Xddd, $Yddd, or
$Zaaa, in which d is any numeric character and a is any alphanumeric character.
Names longer than 5 characters, including the $ sign, are invalid.
If you omit this option, the operating system selects a name for the receiver process.
RESET PROCESS
resets the process-name attribute to the unassigned state and causes the
operating system to select the name for the receiver process. This option is useful
only if you have already issued a SET RECEIVER PROCESS process-name
command, have not yet issued an ADD RECEIVER command, and now decide to
have the operating system select the name.
SLOWMODE {ON | OFF}
During normal processing, the updaters’ RTD values are typically 4 to 20 seconds
behind the extractor’s RTD value. This is expected and normal behavior, although it
does not necessarily mean that the updaters are in fact running 4 to 20 seconds
behind the extractor. The updaters cannot read past what the receiver deems safe,
and that is determined by the frequency with which the receiver updates its context
records. The receiver normally updates its context records every 5 to 15 seconds,
and the updaters’ RTD values reflect that interval.
Some customers would prefer the updaters to have the lowest possible RTD value at
all times. This can be accomplished by setting SLOWMODE ON.