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

REPLICATEPURGE Attribute
The REPLICATEPURGE attribute specifies whether Enscribe purge operations on the primary system
are to be replicated on the backup system.
When set to OFF (the default value), Enscribe purge operations are not replicated. You should use
the default (OFF) for all RDF configurations unless you have a specific need for replicating Enscribe
purge operations.
If you configure the RDF subsystem to replicate network transactions, you should not replicate
Enscribe purge operations because doing so might result in unexpected errors during the updater
network undo processing.
When set to ON, all Enscribe operations on RDF-replicated files are replicated on the backup
system. If you want specific Enscribe files purged, then you must also configure INCLUDEPURGE
and/or EXCLUDEPURGE clauses for each affected updater (see “Updater Processes” (page 84)).
REMOTE MIRROR Attribute
The REMOTE MIRROR attribute specifies whether ZLT is enabled or disabled. The default is off.
For information about the ZLT capability, see Chapter 17 (page 329).
REMOTE STANDBY Attribute
The REMOTE STANDBY attribute specifies the system name of the ZLT standby system. node-name
must be a valid name and must identify a system in your current Expand network. The default is
the name of the backup system. For information about the ZLT capability, see Chapter 17 (page 329).
OWNER Attribute
The OWNER attribute specifies a user ID under which all RDF processes will always run. This
global configuration parameter provides functionality whereby any super ID group user ID can
start and stop RDF.
To illustrate this functionality, imagine ten users are responsible for managing a particular RDF
configuration and that SUPER.RDF is configured as the OWNER. Instead of providing all ten users
access to the SUPER.RDF user ID, each individual user can be assigned a separate super ID group
user ID. If one user is assigned SUPER.FIRST and another SUPER.SECOND, for example, they can
both log on with their user ID and be able to start or stop RDF. The RDF processes do not run under
SUPER.FIRST or SUPER.SECOND, however, but under SUPER.RDF (the RDF OWNER assigned
during configuration). The same principal applies to the other eight users.
The user ID associated with OWNER must be a valid Guardian user ID and must identify an existing
user account on the RDF primary and backup systems. The OWNER must also be a member of the
super ID 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 attribute is omitted, only the user ID that initializes RDF can start or stop RDF (as is
true for all versions of RDF prior to 1.7).
Setting Image Trail Attributes
Use SET IMAGETRAIL and ADD IMAGETRAIL commands to configure the following image trail
attribute:
• ATINDEX
The ATINDEX attribute associates an image trail with a specific audit trail on the primary system.
The RECEIVER RDFVOLUME attribute 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.
Initializing and Configuring RDF 77