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

Do you still wish to start at this point? [Y/N]
Cause In response to your INITIALIZE RDF command and your confirmation to proceed
with that command’s execution, RDFCOM has found the record with the specified TMF
shutdown timestamp in the MAT and RDF is ready to be initialized at that shutdown point.
This message requests your confirmation to proceed further.
Effect If you respond YES or Y, RDF will be initialized at the shutdown point you specified;
when RDF starts, the extractor will begin reading audit at that point in the audit trail. If you
respond NO or N, however, the subsystem will not be initialized.
Recovery This is an informational message; no recovery is required.
Do you wish to proceed? [Y/N]
Cause You entered an INITIALIZE RDF command that attempted to initialize RDF at a
specific TMF shutdown timestamp, and received this message as a prompt for confirmation.
Effect If you respond YES or Y, RDFCOM searches the MAT file for a TMF shutdown
timestamp equal to the one specified. If you respond NO or N, RDF is not initialized.
Recovery This is an informational message; no recovery is required.
Encountered error error# when checking filename
error#
is the file-system error number that identifies the specific error.
filename
is the name of an RDF configuration file on the control subvolume.
Cause While RDF was attempting to check if an RDF control file existed in
$SYSTEM.control-subvolume on the backup system, file-system error error# was
returned.
Effect The INITIALIZE RDF command aborts.
Recovery See the Operator Messages Manual for a description of the error code. For additional
details about understanding and correcting file-system errors, see the Guardian Procedure Errors
and Messages Manual. Analyze and correct the problem, and then retry the INITIALIZE RDF
command.
Error error# obtained in attempting to unpin audit
error#
is the file-system error number that identifies the specific error.
Cause The TMP returned the specified file-system error number when attempting to unpin
a TMF audit-trail file.
Effect The UNPINAUDIT command is ignored.
Recovery See the Operator Messages Manual for a description of the error code. For additional
details about understanding and correcting file-system errors, see the Guardian Procedure Errors
and Messages Manual. Take appropriate corrective action, and then reissue the UNPINAUDIT
command.
Error error# obtaining FILECODE and CRVSN of the MAPFILE filename
error#
is the file-system error number that identifies the specific error.
filename
is the name of the updater mapfile specified in the updater configuration.
Cause RDFCOM could not obtain the file code and CRVSN of the updater mapfile when
an ADD VOLUME, START RDF, START UPDATE, or VALIDATE CONFIGURATION
command was being executed.
Effect The command fails.
RDFCOM Messages 395