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

failure or a STOP command entered manually from TACL. Because the updater might not
have processed all image audit, the RDF TAKEOVER operation cannot be considered
complete. Scan the EMS event log for RDF message 726: this message identifies the updater
process that did not complete TAKEOVER processing.
Effect
Normal purger shutdown processing continues.
Recovery
If UPDATE was OFF at the time of the RDF TAKEOVER, then a second RDF TAKEOVER operation
is automatically started, and no recovery is required. Otherwise, you must restart the takeover
operation with the RDFCOM TAKEOVER command.
726
Updater did not complete the TAKEOVER vol => vol
vol => vol
are the volume on the primary node that the updater is protecting and the corresponding
volume to which it is writing on the backup node.
Cause
The RDF purger has determined that the updater process indicated in this message did not
complete RDF TAKEOVER processing. That updater might have stopped prematurely because
of a double CPU failure or a STOP command entered manually from TACL.
Effect
The updater responsible for the volume named in the message did not complete RDF TAKEOVER
processing.
Recovery
When you have determined why the updater stopped prematurely and you have corrected the
problem, you must re-issue the RDFCOM TAKEOVER command.
727
Audit-trail file missing SNO sno
sno
is the sequence number of the missing audit trail file.
Cause
The specified file should exist on disk, but it does not.
Effect
The extractor abends.
Recovery
This is an internal error. Contact your service provider.
728
Backup Processor Down
Cause
The CPU of the backup process of a NonStop process pair failed.
Effect
The primary process continues to run, but not in fault-tolerant mode.
Recovery
Reload the downed processor. The backup process is re-created when the processor is reloaded.
729
Attempt to alter process priority failed priority
RDF Messages 355