RDF System Management Manual for J-series and H-series RVUs (RDF Update 13)

Cause
A takeover operation is underway.
Effect
The takeover operation continues.
Recovery
This is an informational message; no recovery is required.
TAKEOVER command is not allowed in an OBEY/IN file without the bang (!)
option.
Cause
TAKEOVER command has been issued through an OBEY/IN file without bang (!) option.
Effect
The TAKEOVER operation is aborted.
Recovery
Specify the bang (!) option along with the TAKEOVER command in the OBEY/ IN file or issue
the TAKEOVER command from RDFCOM command prompt.
The control subvolume name is not presently configured for an RDF primary
system. You must use the OPEN command to open an RDF CONFIG file in an
existing RDF control subvolume, or you must initialize a new RDF
configuration with the INITIALIZE RDF command.
name
is the name of the control subvolume explicitly specified or the primary system name assigned
by default.
Cause
The control subvolume either specified or selected by default does not exist.
Effect
The control subvolume remains undefined.
Recovery
Either use the OPEN command to open an RDF CONFIG file in an existing RDF control subvolume,
or initialize a new RDF configuration with the INITIALIZE RDF command.
The control subvolume \sys.$SYSTEM.subvol is not empty. The files on
the control subvolume must be purged. Please note, these files might
belong to another RDF configuration.
sys
is the name of the primary system.
subvol
is the name of the local RDF control subvolume.
Cause
You tried to execute an INITIALIZE RDF command, but RDF control files (such as CONFIG or
CONTEXT) already exist on the local control subvolume.
Effect
The INITIALIZE RDF command aborts.
Recovery
You must purge $SYSTEM.subvol.* on the primary system before you can retry the INITIALIZE
RDF command. Before doing so, however, be sure that the existing files do not belong to a
different RDF configuration that is still valid.
The EXTRACTOR must be a named process
RDFCOM Messages 469