RDF System Management Manual for H-Series and J-Series RVUs (RDF 1.9)

Effect If this message is issued by an updater process, see Table 5-2 in the RDF manual to
determine the appropriate recovery actions.
The extractor retries OPEN calls for the audit trail files if the error is 11 (file missing), 12 (file
in use), or 59 (file is bad). Those errors might occur while the audit trail file is being restored
to disk.
The receiver retries OPEN calls for the image files if the error is 11 (file missing), 12 (file in
use), or 59 (file is bad). Those errors might occur while the image file is being restored to disk.
Recovery If this message is issued by an updater process, see Table 5-2 (page 123) to determine
the appropriate recovery actions.
706
RDF monitor shutdown complete
Cause The monitor process has stopped itself and all RDF processing as the result of an
operator-initiated stop or a catastrophic failure.
Effect The monitor sends a stop message to all RDF processes, and they all successfully shut
down.
Recovery If the operator issued a STOP TMF or STOP RDF command, this message is merely
informational and no recovery is required.
If this message is unexpected, check the RDF log to determine the cause of the failure.
You can attempt to correct the underlying problem, and then restart RDF. If you do that,
however, you should select a convenient time to stop TMF and verify that the primary and
backup databases are synchronized.
You should also check the event log to determine whether the shutdown and startup proceeded
without error. If that is not the case, no recovery is possible.
707
TMF is not yet started
Cause The extractor detected that TMF has not been started yet.
Effect RDF cannot run if TMF is not also running. Normally RDFCOM will recognize that
TMF has not been started and will prevent RDF from starting. In the case of an RDF 707 event,
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, it aborts itself,
and the monitor aborts the receiver and itself.
Recovery You must START TMF before attempting to START RDF.
708
Internal error detected
Cause An internal error has been detected in RDFCOM.
Effect RDFCOM aborts.
Recovery This is an internal error. Contact your service provider.
709
Logfile opened or altered filename
filename
is the name of the new EMS event log (collector).
Cause An RDF process has successfully changed the logfile to the specified EMS Event
Collector.
Effect Messages are now logged to the new collector.
Recovery This is an informational message; no recovery is required.
368 Messages