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

RDF State Requirement
You can issue the INITIALIZE RDF command only when RDF is stopped and no files exist in
the RDF control subvolumes on either the primary and backup systems.
Usage Guidelines
If your RDF subsystem is running and you do not include the TIMESTAMP, INITTIME, or
SYNCHDBTIME options in the INITIALIZE RDF command, then you must stop, delete, and
reconfigure TMF before entering the INITIALIZE RDF command.
Before issuing the INITIALIZE RDF command within an existing RDF configuration, you must
first purge all files from the control subvolume on both the primary and backup systems.
TMF must be started on the primary system, but transaction processing need not be enabled,
when you enter the INITIALIZE RDF command either with or without the TIMESTAMP,
INITTIME, or SYNCHDBTIME options.
The INITIALIZE RDF command creates the configuration and context files for establishment of
a new RDF configuration. After issuing the INITIALIZE RDF command, you must build the new
configuration by entering the appropriate SET and ADD commands or by executing a command
file containing those commands. Only then can you issue the START RDF command to start
RDF.
The INITIALIZE RDF command also establishes the name of the RDF control subvolume, which
you subsequently specify when initiating RDFCOM sessions or in OPEN commands.
If you include the SUFFIX parameter, the specified character becomes a permanent part of the
RDF control subvolume name and you can only alter that character by issuing another INITIALIZE
RDF command.
When using the INITIALIZE RDF command, follow these guidelines:
• If you include the TIMESTAMP option in the INITIALIZE RDF command, then the specified
timestamp must correspond exactly to a TMF shutdown point. Whenever TMF stops in
response to a STOP TMF command, it writes a timestamp in the Event Management Service
(EMS) log. That is the timestamp you use with the TIMESTAMP option of the INITIALIZE
RDF command.
• If you do not include the TIMESTAMP, INITTIME, or SYNCHDBTIME options in the
INITIALIZE RDF command, you must delete and reconfigure TMF before you initialize
RDF. In this case, the extractor will transmit audit from the beginning of the first Master
Audit Trail (MAT) file (AA000001).
• If you include the TIMESTAMP option in the INITIALIZE RDF command, RDFCOM searches
backwards in the MAT for a TMF shutdown record with the specified timestamp. If you
include the INITTIME or SYNCHDBTIME option, RDFCOM searches backwards in the
MAT for the first commit or abort record whose timestamp is less than the specified
timestamp. When it finds the shutdown record or commit/abort record, RDFCOM sets the
context of the extractor to the record following that record.
• When RDF is initialized, the contexts of the receiver and all updaters are initialized to the
beginning of the first image file (AA000001). When RDF is started for the first time after it
has been initialized, any existing image files are purged.
• If you plan to include the TIMESTAMP option in the INITIALIZE RDF command, make
sure that the primary system database is backed up after the TMF shutdown so that the
backup database can be restored at this point in the audit trail. Consider the following
example:
1. TMF and RDF subsystems are running.
2. TMF subsystem is stopped, and RDF subsystem subsequently stops.
3. TMF subsystem is started and application processing resumed.
4. TMF subsystem is stopped.
RDFCOM Commands 201