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

Effect
Validation fails.
Recovery
Before you can validate your local RDF subsystem, you must configure all RDF subsystems in
your network.
If INITIALIZE command is specified in an IN file the pound (#) character
should be used with bang (!) option.
Cause
INITIALIZE RDF command was issued using an IN file to RDFCOM with "#" operator but without
the "!" option.
Effect
The command fails.
Recovery
When issuing the INITIALIZE RDF using an IN file to RDFCOM with "#" operator, specify "!"
operator also.
Illegal File Format: error#
error#
is the NEWPROCESS error number that identifies the specific error.
Cause
A NEWPROCESS error occurred during START RDF or TAKEOVER processing.
Effect
The START RDF or TAKEOVER operation is aborted.
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.
Illegal Home Terminal: error#
error#
is the NEWPROCESS error number that identifies the specific error.
Cause
A NEWPROCESS error occurred during START RDF or TAKEOVER processing.
Effect
The START RDF or TAKEOVER operation is aborted.
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. Correct the error and reenter the START RDF or TAKEOVER command.
Image files needed for Triple Contingency must have been purged because
the receiver’s retaincount must have been set too low.
Cause
Audit required for the COPYAUDIT command on the remote system has been purged, probably
because the receiver’s RETAINCOUNT value was set too low.
Effect
The COPYAUDIT command aborts.
RDFCOM Messages 425