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

Recovery
A subsequent warm start of RDF might be possible, but the success of the restart depends on the
nature of the failure that caused the original process to stop. If the message is issued during ZLT
processing, no recovery is required.
820
RDF receiver stopped unexpectedly, receiver
receiver
is the name of the receiver process that stopped.
Cause
The receiver has stopped unexpectedly. The message includes the name of the stopped process.
Effect
This message is issued by the RDF monitor. The monitor sends an abort request to all remaining
RDF processes to stop RDF.
Recovery
A subsequent warm start of RDF might be possible, but the success of the restart depends on the
nature of the failure that caused the original process to stop.
821
RDF updater stopped unexpectedly, updater
updater
is the name of the updater process that stopped.
Cause
An updater has stopped unexpectedly. The message includes the name of the stopped process.
Effect
This message is issued by the RDF monitor. The monitor sends an abort request to all remaining
RDF processes to stop RDF.
Recovery
A subsequent warm start of RDF will probably be successful, but the success of the restart depends
on the nature of the failure that caused the original updater process to stop.
822
Shutting down in response to ABORT RDF
Cause
An RDF process is being shut down by the RDF monitor following the premature loss of another
RDF process.
Effect
The process stops normally.
Recovery
Scan the EMS event log to determine the original cause of the failure. It might be possible to
restart RDF.
823
Network transaction to be kept: %num num num num
%num num num num
identifies a network transaction.
Cause
This network transaction was committed in the audit trail on the primary system after the first
network transaction marked for undo. It can be kept because it committed prior to the first network
380 Messages