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

Messages
HP NonStop RDF/IMP and IMPX System Management Manual—524388-001
C-16
RDF Messages
probable reason why information could not be obtained is that the file has not been
created yet.
Effect. The updater delays for 30 seconds and then tries to obtain the information
again.
Recovery. If the specified file is an SQL table, then you must create that table on the
remote node.
If the specified file is an Enscribe file, the file may not exist on the RDF backup node
yet. If you have just created the file on the primary node, then the updater has
probably sent the creation audit record to the disk process, but the file has not yet been
created. In this case, this message is informational; when the file is created, the
updater will be able to obtain the information it needs and continue processing.
737
Cause. When the extractor is starting or restarting, it sends a request to the receiver
to obtain its starting position in the TMF audit trail. The extractor issues event 737,
indicating that the extractor is attempting to become synchronized with the receiver by
requesting this starting position.
Effect. The extractor attempts to become synchronized with the receiver.
Recovery. This is an informational message; no recovery is required.
738
sno
is the sequence number of the TMF Master Audit Trail (MAT) for which the
synchronization point was established.
rba
is the relative byte address of the synchronization point.
Cause. This message indicates that te receiver has sent the extractor a starting
position in the TMF audit trail, and the extractor has thereby become synchronized with
the receiver.
Effect. The extractor is synchronized with the receiver.
Recovery. This is an informational message; no recovery is required.
RDF extractor establishing synch
RDF extractor synch established SNO sno RBA rba