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

If TMF was not running previously on the backup system, after you have installed TMF you must
use TMFCOM to issue a START TMF command and one or more ADD DATAVOLS commands to
add to the TMF configuration all disk volumes to be used by the RDF updater processes.
TMF Subsystem Running Previously
If TMF was running on the primary system and you have shut the TMF subsystem down, and if you
have started TMF on the backup system and added the RDF updater volumes to the TMF
configuration, you need not take any other steps with respect to TMF. Proceed to the next task,
described in “Initializing RDF”.
Initializing and Configuring RDF
After initializing and configuring TMF, you are ready to initialize and configure RDF.
Initializing RDF
To initialize RDF, you issue an INITIALIZE RDF command at the primary system. When executed,
this command:
Establishes new configuration and context files for the new RDF configuration (that resides in
the control subvolume)
Identifies the backup system in the configuration
Establishes a starting location in the audit trail where each configured extractor commences
reading audit.
The INITIALIZE RDF command also establishes the name of the RDF control subvolume, which you
must subsequently specify when initiating RDFCOM sessions. If you enter this command for an RDF
configuration that already exists, you must explicitly purge the configuration files and context files
from the control subvolumes on both the primary and backup systems; otherwise, an error message
will appear. This requirement helps ensure that you do not accidentally destroy the wrong RDF
configuration in cases where multiple RDF configurations exist for replication to multiple backup
systems.
NOTE: Previously you were required to purge the RDF control subvolumes on the primary and
backup systems before you could run the RDFCOM Initialize RDF command (see details on RDF
control subvolume in Chapter 4 (page 91)). You can now specify a special option that automatically
purges the existing control subvolume on the primary and backup system as part of the RDF
initialization command. For complete information on INITIALIZE RDF, see Chapter 8 (page 176).
If you are going to replicate database changes to multiple backup systems, you must also specify
a one-character control subvolume suffix in the INITIALIZE RDF command for individual
configurations. If you specify a suffix character, the control subvolume name is the name of the
primary system without the backslash and with the suffix character appended to it. If you omit the
suffix character, the control subvolume name is the name of the primary system without the backslash
and without a suffix character.
As a general rule, you can only issue the INITIALIZE RDF command if all of the following conditions
exist:
TMF is initialized.
RDF is not running.
You are logged on under TACL as a member of the super ID group.
You have a remote password from the primary system to the backup system. (It is recommended,
but not required, that you have a remote password from the backup system to the primary
system as well.)
72 Installing and Configuring RDF