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

1. TMF writes a shutdown record to the MAT. When the master extractor reads the shutdown
record, it notifies the monitor that TMF has stopped.
NOTE: If the extractor process falls way behind TMF because the communications lines to
the backup system have been down and come up again, it can take some time for the extractor
to get to the TMF shutdown record. The extractor stops processing the audit trail files when it
cannot communicate with the receiver and resumes processing when the communications lines
are restored.
2. The master extractor stops as soon as the master receiver replies that it has processed the TMF
shutdown record.
3. The RDFNET process (if there is an RDF network) does not wait for any other process to stop;
it merely stops when informed to do so.
4. If updating is enabled, each updater process stops when it reaches the TMF shutdown record
in its image trail.
5. The purger stops after all the updaters have stopped.
6. The receiver(s) stop when the purger has stopped.
7. The monitor stops after all the other RDF processes have stopped.
If you stop TMF and then restart it before RDF can read the shutdown record, RDF stops when it
encounters the shutdown record. If that happens, you need to issue a START RDF command to
restart RDF.
NOTE: TMF does not start RDF, which means that if you start TMF, you must then explicitly start
RDF.
If the communications lines are down when you stop TMF, the extractor continues to run, but it will
not recognize that TMF is shut down because the extractor does not read the data in the MAT until
the extractor can transmit data to the receiver on the backup system. If the extractor is not reading
the MAT, it cannot encounter the TMF shutdown message. Two situations could arise:
• If the communications lines come back up before you restart TMF, RDF encounters the TMFCOM
STOP TMF record in the MAT and then stops processing.
• If the communications lines are down and you feel you really must stop the RDF system
irrespective of the TMF shutdown record, you must issue the STOP RDF command on both the
primary and backup systems. In this case, RDF stops processing without reading to the TMF
shutdown record in the MAT.
When you restart TMF, you must then restart RDF. RDF begins processing at the point where
it stopped. When RDF reads the TMF shutdown record associated with the preceding TMF
shutdown, RDF shuts down. You must then restart RDF again by issuing another START RDF
command.
When you shut down RDF by issuing a TMFCOM STOP TMF command, you can use successive
STATUS RDF commands to determine when all of the RDF processes have stopped.
Stopping RDF From the Primary System
When you issue the STOP RDF command on the primary system, all RDF processes stop immediately
without processing to the end-of-file mark in the MAT (except the updaters, which might continue
for a short while to finish up their work in progress).
While RDF is running, the database on the backup system is always in an inconsistent state because
updaters apply audit asynchronously with regard to one another. When you stop RDF by issuing
an STOP RDF command, the updaters stop immediately and they leave the backup database in
an inconsistent state. This is also true whenever you issue the STOP UPDATE command.
Stopping RDF 125