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

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.
The number of physical UPDATEVOLUMES exceeds 255. RDF/IMPX is required
for this many volumes.
Cause
RDF has detected that the user is running RDF/IMP and the total number of physical volumes for
all UPDATEVOLUMEs exceeds 255. This can happen where some, or all, of the UPDATEVOLUMEs
are SMF virtual disks.
Effect
RDF will not start.
Recovery
Upgrade the RDF software to RDF/IMPX or reconfigure your disks on the RDF backup node so
that the total number of physical disks for all the UPDATEVOLUMEs is less than 255.
The PURGER must be a named process
Cause
You must specify a process name for the purger process before issuing an ADD command.
Effect
The start command fails.
Recovery
You must reconfigure RDF with a named purger process.
The RDF primary system in the environment you are attempting to copy
audit from does not match the primary system in this environment.
Cause
The COPYAUDIT command detected that the RDF primary system in the RDF environment you
are attempting to copy audit from is not the same as the RDF primary system in the local
environment.
RDFCOM Messages 459