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

File is not an edit file filename.
filename
is the name of the user-specified file for generating the report.
Cause
When a VALIDATE CONFIGURATION or LIST UPDATERFILEOPENS command is executed,
RDFCOM determines that a user specified file name for report generation already exists and it
is not an edit file.
Effect
The command fails.
Recovery
Provide an EDIT file and reenter the command.
Fixing up context to enable another RDFCOM Takeover command
Cause
The COPYAUDIT command has finished copying the missing audit from the remote system to
the local system, and is now about to update context records to permit execution of another
TAKEOVER command.
Effect
RDF begins to update the context records.
Recovery
This is an informational message; no recovery is required.
Fixing up the ZFILEINC file to enable another RDFCOM Takeover command
Cause
The COPYAUDIT command has finished copying the missing audit from the remote system to
the local system, and is now about to copy the ZFILEINC file from the remote system to the local
system.
Effect
RDF begins to copy the ZFILEINC file.
Recovery
This is an informational message; no recovery is required.
Global record not found for subsystem ctrl-subvol
ctrl-subvol
is the name of an RDF subsystem control subvolume.
Cause
The global record of the RDF subsystem with the specified control subvolume could not be found.
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.
436 Messages