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

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.
The Triple Contingency COPYAUDIT command has completed successfully.
You must now issue a new RDFCOM Takeover command.
Cause
The COPYAUDIT command has finished copying the missing audit from the remote system to
the local system and has updated all context records on the local system.
Effect
The context records are updated.
Recovery
This is an informational message; no recovery is required.
The total number of items in the INCLUDE, EXCLUDE, INCLUDEPURGE, and
EXCLUDEPURGE lists has exceeded 100.
Cause
The total number of items in the INCLUDE, EXCLUDE, INCLUDEPURGE, and EXCLUDEPURGE
lists, are more than 100.
Effect
The volume is not added for RDF protection.
Recovery
Reduce the total number of items in the INCLUDE, EXCLUDE, INCLUDEPURGE, and
EXCLUDEPURGE lists to less than or equal to 100.
The UPDATER must be a named process
Cause
You must specify a process name for the updater process before issuing an ADD command.
Effect
The start command fails.
Recovery
You must reconfigure RDF with a named updater process.
The year must be greater than 1996.
Cause
You specified the year of a timestamp that is earlier than 1997.
Effect
The command involving the timestamp fails.
RDFCOM Messages 461