RDF/IMP, IMPX, and ZLT System Management Manual

Messages
HP NonStop RDF/IMP, IMPX, and ZLT System Management Manual—524388-002
C-51
RDF Messages
848
Cause. The extractor has sent the maximum number of messages to the receiver and
has not received any replies for at least five minutes.
Effect. The extractor cannot proceed any further.
Recovery. This is not an RDF problem. You should investigate your Expand network
and take corrective action. If necessary, you can issue a STOP RDF command on
both the primary and backup systems to stop the RDF processes in an orderly fashion.
849
Cause. TMF was stopped during an RDF online database synchronization operation,
before the extractor had completed its phase one processing.
Effect. The extractor abends because the database synchronization operation can no
longer succeed.
Recovery. You must reinitialize the RDF product and restart the online database
synchronization operation.
850
Cause. TMF was stopped during an RDF online database synchronization operation,
after the extractor had completed its phase one, part 1 processing.
Effect. The extractor completes phases one and two of its database synchronization
processing and then shuts down in response to the TMF shutdown audit record.
Recovery. Informational message only; no corrective action is needed. When you
restart the RDF product, ensure that the duplicate database tables and files have been
moved to the backup system before you start the updaters.
851
Cause. The RDF product cannot support an environment where transactions involving
the RDF primary system have originated on more than 48 different nodes. The
receiver has encountered transactions that have originated on more than 48 nodes.
Effect. The receiver abends and the RDF system aborts.
RDF extractor waiting for network reply
TMF Shutdown before phase one of database synchronization
TMF Shutdown during phase one of database synchronization
Too many nodes in network transactions.