RDF System Management Manual for H-Series RVUs (RDF 1.8)

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
• Indicates where in the MAT RDF should begin operations
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
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.
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-user 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.)
For complete information about the INITIALIZE RDF command, see the description of the
INITIALIZE RDF command in Chapter 8 (page 173).
To a TMF Shutdown Timestamp
If TMF was running previously on the primary system and did not need to be initialized and
configured, you can initialize RDF to a timestamp that reflects the time of the last TMF shutdown.
To issue the INITIALIZE RDF command without first initiating an RDFCOM session, enter the
command in the following format in response to the TACL prompt. In the TIMESTAMP parameter,
be certain to specify the exact time (to the minute) that TMF was last shut down. You determine
the appropriate timestamp by examining previous TMF messages in the EMS log. In this example,
the TIMESTAMP parameter specifies 1:32 p.m., January 7, 1999:
>RDFCOM;INITIALIZE RDF, BACKUPSYSTEM \CHICAGO,
SUFFIX A, TIMESTAMP 7JAN1999 13:32
Initializing and Configuring RDF 83