RDF System Management Manual for H-Series RVUs (RDF 1.8)

Recovery See the Operator Messages Manual for a description of the error code. For additional
details about understanding and correcting process errors, see the Guardian Procedure Errors
and Messages Manual. If possible, correct the error and reenter the command that encountered
the error. Otherwise, see your system manager.
Synch point for synchdbtime has been found
synchdbtime
is a SYNCHDBTIME timestamp specified previously by an operator in an RDFCOM
INITIALIZE RDF command.
Cause In conjunction with a complete database synchronization, a record whose timestamp
is less than synchdbtime has been located successfully.
Effect The RDFCOM INITIALIZE RDF command continues.
Recovery This is an informational message; no recovery is required.
Synch timestamp is synchdbtime
synchdbtime
is a SYNCHDBTIME timestamp specified previously by an operator in an RDFCOM
INITIALIZE RDF command.
Cause In conjunction with a complete database synchronization, you are attempting to
initialize RDF to a timestamp that is earlier than the current time. A record whose timestamp
is less than synchdbtime has been found, and synchdbtime has been stored in the RDF
configuration record.
Effect The RDFCOM INITIALIZE RDF command continues.
Recovery This is an informational message; no recovery is required.
TAKEOVER in progress
Cause A takeover operation is underway.
Effect The takeover operation continues.
Recovery This is an informational message; no recovery is required.
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 name is not empty. The files on the control
subvolume must be purged. Please note, these files might belong to
another RDF configuration.
name
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.
RDFCOM Messages 421