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

lines are up. In addition to stopping TMF, this action stops all RDF processes and saves the context
of each process in a file. Alternatively, if you have multiple applications running on your primary
system and not all of the databases are RDF-protected, then stopping TMF to coordinate a planned
and synchronized shutdown may not be possible. In this case, you can perform an ordered stop
(do not perform a TACL stop that would then cause in-flight transactions to be aborted by TMF) of
the applications updating the RDF-protected database, and when you are certain they have
completed, then issue the STOP RDF, DRAIN command. Because your applications have stopped,
then the RDF-protected database on the primary system is closed and is in the same state as if TMF
was stopped. See “Critical Operations, Special Situations, and Error Conditions” (page 113) for a
discussion on how this operation may be of value to you.
For information about when to use the STOP RDF command and how it affects the primary and
backup databases, see “Stopping RDF” (page 124).
There are three ways to stop RDF:
• Issue a STOP TMF command at the primary system.
When you issue the TMFCOM command STOP TMF, RDF also shuts down after RDF encounters
the TMF shutdown record in the MAT. This method ensures that the primary and backup
databases are logically identical with one another when RDF stops. When you restart RDF,
the context file directs RDF where to resume.
• Issue a STOP RDF command at the primary system.
If the decision has been made to stop RDF without stopping TMF, issue a STOP RDF command
at the primary system. RDF stops immediately after all RDF processes save context information
in the context file.
• Issue a STOP RDF command at the backup system.
You should use this method of stopping RDF only if one of the following two conditions is true:
◦ The RDF monitor process is not running on the primary system.
◦ All communications lines to the primary system are down.
If the decision has been made to stop RDF on the backup system, issue a STOP RDF
command at the backup system. All processes running on the backup system write context
information to a context file and then stop.
If the communications lines between the primary and backup systems are up, a STOP
RDF command issued at the backup system fails, and RDFCOM displays an error message.
NOTE: Before you can restart RDF, you must stop RDF on the primary system as well.
When RDFCOM executes the STOP RDF command, it writes a message to the RDF log file indicating
this action.
Updaters cannot always respond immediately to a STOP RDF command. If an updater has audit
records queued for the disk process, the updater must wait until all of that information is processed
before it can shut down.
If RDF appears to be hung and unable to shutdown, you can stop the RDF by issuing the following
TACL command:
SSTATUS *. PROG, $SYSTEM.RDF.*, STOP
This assumes your RDF software is in $SYSTEM.RDF. If you have set the RDF SOFTWARELOC
attribute to a different location, use that location instead of $SYSTEM.RDF.
CAUTION: Issuing this command in this situation is only safe, however, if this is the backup system
for a single RDF environment.
240 Entering RDFCOM Commands