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

Recovery
Restart RDF and the STOP TMF record will be processed as normal. Once RDF has stopped as
a result of the STOP TMF record, RDF can be restarted and a new STOP RDF, DRAIN (or REVERSE)
command can be issued.
919
Extractor will try again to process a critical audit record
Cause
The extractor has encountered a critical audit record that pertains to either a STOP TMF operation
or a NonStop SQL/MP or NonStop SQL/MX DDL operation WITH SHARED ACCESS, and the
Monitor was unable to communicate information about the operation to another RDF process.
See the most recent RDF Event 701 for details.
Effect
The extractor delays for a short period of time and then tries to process this audit record again.
Recovery
See the most recent RDF event 701 and take corrective action. When you have corrected that
problem, the extractor can proceed with processing this critical audit record.
920
[Exception Reason: exception-cause ]
[ An unknown exception occurred, type type ]
exception-cause
is the cause for the exception.
type
is the unknown exception type.
Cause
The specified process has encountered a critical exception and has trapped. If possible, the
event will have a text description of the reason for the exception. If not, the numeric type of the
exception is indicated.
Effect
The process abends, and RDF will abort.
Recovery
Take corrective action to alleviate the cause of the exception, if possible, and restart RDF. If the
cause of the exception is not immediately obvious, contact your service provider.
921
The updater's MAPFILE filename is not an edit file.
Cause
The updater has detected that the mapfile is not an edit file.
Effect
The updater stops and RDF aborts.
Recovery
Provide an edit file, then restart RDF.
922
Mapping string mapping-string is invalid [ at position index ] in the
MAPFILE filename. Cause cause
mapping-string
identifies the invalid mapping string.
RDF Messages 405