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

Recovery
If all files of the MAT are currently on disk (for instance, the files from AA000001 to the current
audit file), then the specified timestamp is earlier than the last time TMF was initialized. To
recover, you need to reexamine the EMS log or the OPRLOG for a later TMF shutdown point or
stop TMF and use that shutdown point.
If the shutdown record is located in an audit file that is no longer on disk, you will need to restore
that file to disk, as well as all files between it and the latest file, and then reenter the command.
For example, if files AA000009 through AA000010 are currently on disk, and the shutdown
record is located in AA000007, then you must restore AA000007 through AA000008 to disk.
Alternatively, you can use a different TMF shutdown point that is located in a MAT file still on
disk, or you can stop TMF and use that resulting shutdown point.
START RDF Aborted
Cause
A START RDF command aborted.
Effect
The command fails.
Recovery
Scan the EMS event log to determine why the command aborted, correct the error if possible,
and reenter the START RDF command.
START UPDATE in progress, Please Wait...
Cause
A START UPDATE command is being executed.
Effect
The start operation continues for the updater process.
Recovery
This is an informational message; no recovery is required.
Starting RDF, Please Wait...
Cause
A START RDF command is being executed.
Effect
The start operation continues for RDF.
Recovery
This is an informational message; no recovery is required.
STATUS RDF (\primary-> \backup) is NOT running
primary
is the name of the primary node in the RDF configuration.
backup
is the name of the backup node in the RDF configuration.
Cause
A STATUS RDF command was issued while RDF was not running.
Effect
The command fails.
Recovery
Enter another command, or wait until RDF is started and then reenter the STATUS RDF command.
STOP SYNCH command is aborted.
466 Messages