RDF/IMP and IMPX System Management Manual (RDF 1.3+)

Messages
Compaq NonStop™ RDF/IMP and IMPX System Management Manual—522204-001
C-5
RDF Messages
You can attempt to correct the underlying problem, and then restart RDF. If you do that,
however, you should select a convenient time at which to stop TMF and verify that the
primary and backup databases are synchronized.
You should also consult the EMS event log to determine whether the shutdown and
startup proceeded without error. If that is not the case, no recovery is possible.
707
Cause. The extractor detected that TMF has not been started.
Effect. RDF cannot run if TMF is not also running. Normally, RDFCOM will discover
that TMF has not been started and will prevent RDF from starting. In the case of RDF
error 707, TMF was running when RDFCOM verified that TMF was started, but TMF
was then stopped before the extractor was started. If the extractor detects that TMF is
not started, the extractor aborts itself, and the monitor aborts the receiver and itself.
Recovery. Start TMF before trying to start RDF.
708
Cause. RDFCOM detected an internal error.
Effect. RDFCOM aborts.
Recovery. This is an internal error. Contact your service provider.
709
filename
is the name of the new EMS event log (collector).
Cause. An RDF process has successfully changed the EMS event log to the specified
collector.
Effect. Messages are now logged to the new collector.
Recovery. This is an informational message; no recovery is required.
Note. If TMF dumps any audit trail files to disk while RDF is stopped, you must either restore
the dumped files to disk or resynchronize the primary and backup databases before restarting
RDF.
TMF is not yet started
INTERNAL ERROR detected
Log File Opened or Altered filename