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

The userid associated with OWNER must be a valid Guardian userid and must identify an
existing user account on the RDF primary and backup systems. The OWNER must also be a
member of the super-user group, since that is an existing requirement in RDF for stopping and
starting RDF.
OWNER is an unalterable value. There is no need to change the value, unless you configured it
incorrectly (in which case you must reinitialize RDF with the correct value).
If the OWNER parameter is omitted, only the userid that initializes RDF can start or stop RDF
(as is true for all versions of RDF prior to 1.7).
Setting Image Trail Parameters
Use SET IMAGETRAIL and ADD IMAGETRAIL commands to configure the following image
trail parameter:
• ATINDEX
The ATINDEX parameter associates an image trail with a specific audit trail on the primary
system.
The RECEIVER RDFVOLUME parameter specifies the disk volume that contains the receiver’s
master image trail. The receiver process writes all commit/abort records to this volume. All
updaters must be configured to secondary image trails.
To create secondary image trails, use the ADD IMAGETRAIL command. Later, when you
configure your individual updater processes, you assign each of these processes to a specific
image trail. By spreading updaters across secondary image trails, you reduce the number of
updaters contending for a specific trail. ATINDEX specifies which receiver will write to that trail;
0 is the default.
Each secondary image trail contains the audit records needed by the associated updater processes.
Image trail files in secondary image trails have the same extent sizes as image trail files on the
volume specified by RDFVOLUME.
NOTE: To have secondary image trails, you must add them after initialization and before RDF
has been started for the first time. Also you cannot add secondary image trails until you have
configured the receiver, as described in the previous paragraphs. The secondary image trail files
have the same extents as the master image trail files. To delete a secondary image trail, you must
stop RDF, delete any updaters associated with the particular trail, and then delete the trail.
Normally, you should never delete a secondary image trail until RDF has completely caught up
with TMF.
To add one secondary image trail to the volume named $IMAGA1 and another to the volume
named $IMAGA2, issue the following commands:
]SET IMAGETRAIL ATINDEX 0
]ADD IMAGETRAIL $IMAGA1
]SET IMAGETRAIL ATINDEX 1
]ADD IMAGETRAIL $IMAGA2
Setting Trigger Parameters
Use SET TRIGGER and ADD TRIGGER commands to configure the following trigger parameters:
• PROGRAM
• INFILE
• OUTFILE
• CPUS
• PRIORITY
• WAIT or NOWAIT
Initializing and Configuring RDF 91