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

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 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.
Recovery Reissue the command, specifying a timestamp year that is 1997 or greater.
This aux EXTRACTOR Record already exists.
Cause You tried to add an EXTRACTOR with a particular ATINDEX value, but there is
already one configured with that value.
Effect The ADD command fails.
Recovery Review and revise your RDF configuration.
This aux RECEIVER Record already exists.
Cause You tried to add an RECEIVER with a particular ATINDEX value, but there is already
one configured with that value.
Effect The ADD command fails.
Recovery Review and revise your RDF configuration.
This command is not allowed in an OBEY file.
Cause An illegal command was encountered within an OBEY command file.
Effect The command fails.
Recovery Remove the command from the OBEY command file, and reenter the command
directly from your terminal.
This RDF subsystem is not configured in the network master subsystem
Cause Your current RDF subsystem is not listed in your the configuration of your network
master.
Effect Validation fails.
Recovery You must reconfigure your network master and possibly your local configuration.
TMF is having trouble.
Cause There is a problem with TMF.
Effect The configuration validation fails.
Recovery Check the status of TMF. When TMF is operational, reenter the command.
TMF is not configured.
Cause TMF has not been configured.
Effect The requested RDFCOM operation fails.
Recovery Configure and start TMF, and request the RDFCOM operation again.
RDFCOM Messages 425