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

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 cannot alter it. If you want to change it, you must reinitialize RDF
again and specify a new suffix character. Note, however, that if you reinitialize RDF with a new
suffix character, you should remember to purge the control subvolume and image trails of the
previous configuration you are replacing.
When using the INITIALIZE RDF command, follow these guidelines:
• The INITTIME option is particularly useful for initializing RDF without having to STOP TMF. For
example, if you have been running RDF 1.8, you have stopped RDF, and you have just installed
the RDF 1.9 software, use the INITTIME option instead of having to stop TMF. See Chapter 3
(page 62) for a discussion on this type of operation.
• The SYNCHDBTIME is the option you would use when performing an online database
synchronization operation. For a full discussion on this option used in conjunction with a
complete or partial database synchronization, see Chapter 7 (page 158).
• If you include the TIMESTAMP, INITTIME, or SYNCHDBTIME options in the INITIALIZE RDF
command, the initialization will complete much quicker if all the files from the current down
to the one in which the timestamp being sought is located are all on disk. If, however, some
of these audit files have been dumped to tape, RDFCOM triggers TMF to prompt you to restore
needed audit trail files. Therefore, not every file in the MAT must be present in the audit trail
at the time you issue the INITIALIZE command. For example, if the current file is AA000010,
files AA000010 and A000009 are in the MAT, and A000008 contains the point where RDF
is actually initialized but it has already been dumped to tape, then RDFCOM triggers TMF to
prompt you to restore AA000008. When you have restored that file, RDFCOM continues its
search in A000008 for the correct initialization location.
• 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 previously existing image files are purged.
204 Entering RDFCOM Commands