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

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.
710
TMP is inaccessible
Cause
An RDF process has tried to obtain audit trail information from the TMF management process
pair (TMP), but the TMP was not accessible. The probable cause is that TMF is not currently
running. RDF requires that TMF be up and running on the primary and all backup nodes.
Effect
The RDF process abends.
Recovery
You must start the TMF product on the affected node.
711
Failure to get process info - error error
error
is the file-system error number that identifies the specific error.
350 Messages