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

To issue the INITIALIZE RDF command from within an RDFCOM session, enter the following
in response to the RDFCOM prompt:
]INITIALIZE RDF, BACKUPSYSTEM \CHICAGO, SUFFIX A,
TIMESTAMP 7JAN1999 13:32
If the INITIALIZE RDF commands in this discussion were issued from the primary system
\DALLAS, RDF would respond by creating a configuration file in the control subvolume named
$SYSTEM.DALLASA.CONFIG.
Without a TMF Shutdown Timestamp
If you have just installed (or deleted and reinstalled) TMF so that it starts at relative byte address
(rba) 0 in audit-trail file sequence number 1, you should now issue an INITIALIZE RDF command
without the TIMESTAMP parameter at the TACL prompt on the primary system:
>RDFCOM; INITIALIZE RDF, BACKUPSYSTEM \BOSTON, SUFFIX A
When you begin an RDFCOM session on a system in which RDF has never been previously
initialized (such as \PRIMSYS, for example), RDFCOM responds with the following prompt:
***Warning*** The control subvolume PRIMSYS is not presently
***Warning*** configured for an RDF primary system.
You must use the OPEN command to open an RDF CONFIG file in an
existing RDF control subvolume, or you must initialize a new RDF
configuration with the INITIALIZE RDF command.
To continue with the session, you must either enter an INITIALIZE RDF command, or use the
OPEN command as directed in Chapter 8 (page 173).
Initializing RDF Without Stopping TMF
The INITIALIZE RDF command includes a parameter, INITTIME inittime , that you can use
to initialize the RDF product without stopping TMF or your applications.
There are two cases where you would use this capability:
• If you want to install a new version of the RDF product and you cannot afford to stop TMF
even momentarily to get a TMF shutdown timestamp.
• If you are running RDF and encounter a problem for which you would like to reinitialize it
without having to resynchronize your databases.
Determining a Valid inittime Value
When using the INITTIME parameter without the NOW clause, it is important that you specify
a valid inittime value.
To do so, first issue a STATUS RDF command and take note of the highest updater RTD time.
Then round that RTD time up to the next higher minute (0:43 becomes 1:00, 1:27 becomes 2:00,
3:04 becomes 4:00, and so forth). Finally, subtract that rounded-up time from the current system
time shown in the status display.
inittime := (current-system-time — rounded-highest-updater-RTD-time)
RDFCOM then subtracts an additional three minutes from the specified timestamp. This is to
ensure that the extractor’s starting position is at a point in the MAT where RDF had previously
sent audit information to the backup system and the updaters had applied it to the backup
database. This practice guarantees that no audit information will be lost during initialization.
When you include the INITTIME parameter in the INITIALIZE RDF command, RDFCOM initiates
a backward scan of the MAT searching for the first commit or abort record whose timestamp is
less than the specified inittime . When RDF is subsequently restarted, some of the audit
information will be reapplied to the backup database. This does not cause any inconsistencies
between the primary and backup databases, but rather ensures that they stay completely
synchronized with one another.
84 Installing and Configuring RDF