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

The RDF primary system in the environment you are attempting to copy
audit from does not match the primary system in this environment.
Cause The COPYAUDIT command detected that the RDF primary system in the RDF
environment you are attempting to copy audit from is not the same as the RDF primary system
in the local environment.
Effect The COPYAUDITcommand aborts.
Recovery Correct the REMOTESYS remote-sys and REMOTECONTROLSUBVOL rcvs
parameters and reissue the COPYAUDIT command.
RDFNET must be a named process
Cause You must specify a process name for the RDFNET process before issuing an ADD
command.
Effect The start command fails.
Recovery You must reconfigure RDF with a named RDFNET process.
The [remote] control subvolume name [on bksys] is not empty. The files
on the control subvolume must be purged. Please note, these filess might
belong to another RDF configuration.
name
is the name of the remote RDF control subvolume.
bksys
is the backup system name.
Cause You tried to execute an INITIALIZE RDF command, but the RDF control files (such
as CONFIG or CONTEXT) already exist on the remote control subvolume. If these files are on
the backup system, then that name is specified.
Effect The INITIALIZE RDF command aborts.
Recovery You must purge \system.name.* on the backup systems 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 specified timestamp cannot be in the future
Cause You have specified an INITTIME timestamp that is in the future rather than in the
past.
Effect The INITIALIZE RDF command aborts.
Recovery Reissue the STOP UPDATE, TIMESTAMP command, specifying a timestamp that
is earlier than the current system time as shown in the status display.
The specified timestamp must be at least five minutes greater than the
current time
Cause The timestamp specified in a STOP UPDATE, TIMESTAMP command is less than
five minutes from the current time.
Effect The STOP UPDATE command aborts.
Recovery Reissue the STOP UPDATE, TIMESTAMP command, specifying a timestamp that
is at least five minutes ahead of the current time.
The STOP SYNCH command is aborted because it has been issued previously.
Cause You are attempting to execute an RDFCOM STOP SYNCH command, but the
command has already been issued previously.
Effect The RDFCOM STOP SYNCH command aborts.
Recovery You can only execute the STOP SYNCH command if the RDF product is currently
involved in online database synchronization. Because the STOP SYNCH command has already
been issued, this is an informational message; no recovery is required.
424 Messages