RDF System Management Manual for H-Series and J-Series RVUs (RDF 1.9)

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
TMF Shutdown during phase one of database synchronization
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 This is an informational message; no recovery is required. 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
Too many nodes in network transactions
Cause The RDF product cannot support an environment where transactions involving the
RDF primary system have originated on more than 255 different nodes. The receiver has
encountered transactions that have originated on more than 255 nodes.
Effect The receiver abends and the RDF system aborts.
Recovery Recovery is not possible. Contact your service provider.
852
STOP RDF, DRAIN completed. All updaters have stopped
Cause A STOP RDF, DRAIN command has completed successfully.
Effect This RDF environment shuts down.
Recovery This is an informational message; no recovery is required.
853
Purger TST filled
Cause In determining what transactions need to be undone, the internal table of transactions
has become filled.
Effect RDF aborts.
Recovery Contact your service provider for assistance with recovering from this situation.
854
ZTXUNDO file cannot be opened
Cause While attempting to write the list of transactions that need to be undone to the
ZTXUNDO file, that file could not be opened.
Effect RDF aborts.
Recovery If the operation involves an RDF takeover, take corrective action to enable the file
to be opened and then reissue the TAKEOVER command.
If the operation involves a stop-update-to-time operation, take corrective action to enable the
file to be opened and then restart RDF. If you still want to bring the backup database into a
consistent state, you will need to issue a new STOP UPDATE, TIMESTAMP timestamp
command specifying a new timestamp.
398 Messages