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

ALTER of this element cannot be performed with RDF up
Cause
An ALTER command was issued for a non-runtime ALTER option.
Effect
The command fails.
Recovery
Either shut down RDF and reenter the ALTER command, or select another command to enter.
ALTER of this element cannot be performed with updaters running
Cause
An ALTER command was issued for a non-runtime ALTER option.
Effect
The command fails.
Recovery
Stop updating by entering the STOP UPDATE command through RDFCOM, and then reenter the
ALTER command.
ALTER RECEIVER RDFVOLUME is no longer supported
Cause
RDFCOM no longer supports this command.
Effect
The command fails.
Recovery
Select another command.
Ambiguous timestamp for operation
Cause
RDFCOM could not resolve an ambiguous timestamp after a change to Local Civil Time (LCT)
when the LCT was changed relative to Greenwich Mean Time (GMT). In this situation, two LCTs
map to the same GMT and it is impossible to determine the correct intended time.
This problem typically occurs in Autumn, when the clock is set back from Daylight Savings Time.
If you specify an RDF initialization timestamp between 1:00AM and 2:00AM on that day, the
intended time is ambiguous. Did you mean before the clock was turned back or after? To eliminate
this ambiguity, a specified RDF initialization timestamp in this one-hour interval is reported as
an error.
Effect
Initialization is aborted.
Recovery
Reinitialize RDF specifying a timestamp that is earlier than the ambiguous time.
A partial RDF TAKEOVER has completed
Cause
You issued a STATUS RDF command after a TAKEOVER command has completed, but one or
more updater processes had terminated prematurely and was therefore unable to process all
applicable image audit data.
Effect
The primary and backup databases are inconsistent.
RDFCOM Messages 409