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

error#
is the file-system error number that identifies the specific error.
Cause
Create operation returned an error when RDFCOM tried to create the updater maplog file when
an ADD VOLUME, ALTER VOLUME, START UPDATE, or START RDF command was being executed.
Effect
The command fails.
Recovery
See the Guardian Procedure Errors and Messages Manual for a description of the recovery
actions for the file-system error. Correct the error indicated by error#, then reenter the command.
The MAPLOG file filename should be an edit file
filename
is the name of the updater maplog specified in the updater configuration.
Cause
RDFCOM found that the updater maplog is not an edit format file when an ADD VOLUME, ALTER
VOLUME, START RDF, or START UPDATE command was being executed.
Effect
The command fails.
Recovery
Provide an edit file and reenter the command.
The MAT file with sequence number seq-num is not currently on disk.
RDFCOM can trigger the restoration of the file, but only as a waited
operation and you must mount the tapes Do you want RDFCOM to restore
the file?
seq-num
is the sequence number of the MAT file.
Cause
While searching for a TMF shutdown timestamp to use to initialize RDF, RDFCOM found that
the audit trail file with the specified sequence number is not currently available.
If you respond to the prompt with YES or Y, RDFCOM directs the TMP to begin restoring this
file.
NOTE: If the file was dumped to tape, you must wait for the TMP to prompt you to mount the
tape. This mount request is logged in the EMS log.
If you respond with NO or N, then RDFCOM aborts the initialization attempt.
Effect
RDFCOM waits for your response to the prompt.
Recovery
Respond YES or Y, or NO or N, to the prompt.
The MONITOR must be a named process.
Cause
You must specify a process name for the monitor process before issuing an ADD command.
Effect
The start command fails.
Recovery
You must reconfigure RDF with the named monitor process.
RDFCOM Messages 471