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

Messages
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
C-20
RDF Messages
Cause. Either TMF has not been started on the remote node, or the volume
associated with this updater on the remote node has not been added as a datavol in
the TMF configuration. TMF must be started on the remote node, and the volume
associated with this updater on the remote node must be added as a datavol to this
remote TMF configuration.
Effect. The updater will not start.
Recovery. Start TMF on the remote node and add the associated volume as a data
volume in the TMF configuration. Additionally, you should start the volume for
transaction processing.
748
Cause. The extractor detected an audit record of an unknown version.
Effect. The extractor process abends.
Recovery. This is an internal error. Contact your service provider.
749
Cause. The extractor detected an audit record generated by an unknown version of
TMF.
Effect. The extractor abends.
Recovery. Reinitialize RDF. You might also need to resynchronize the primary and
backup databases.
750
Cause. All RDF processes rely upon the ability to post timers by calling
SIGNALTIMEOUT and take action when those timers expire. This message indicates
that a call to SIGNALTIMEOUT failed because there were insufficient time list elements
(TLEs) available.
Effect. The process continues to run, but recovery is required.
Recovery. Issue a STOP RDF command immediately. Then investigate why there is
a shortage of TLEs in the CPU of the RDF process that could not obtain one. If you
want to start RDF again while conducting this investigation, you should alter the RDF
configuration of the process that could not obtain the TLE, specifying a different set of
CPUs for that process.
Internal error - RDF extractor abending
Old audit record format encountered
Failure to obtain TLE for SIGNALTIMEOUT