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

UPDATEREXCEPTION {ON | OFF}
specifies the manner in which exception files are used.
When set to ON (the default value), the updaters log an exception record for each and every
audit record they must undo during a takeover.
When set to OFF, the updaters log exception records only for the first and last audit records
that must be undone (the minimum logging necessary to support Triple Contingency
operation).
LOCKSTEPVOL $volume
specifies the primary system disk volume on which the RDF lockstep file
(ZRDFLKSP.control-subvolume) is to be located. The specified volume must be configured
to the Master Audit Trail (MAT), and either the entire volume or at least the lockstep file
must be protected by the RDF subsystem. For information about the RDF lockstep capability,
see Chapter 15 (page 289).
REPLICATEPURGE {ON | OFF}
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, Enscribe purge operations on the primary system are replicated on the
backup system.
REMOTE MIRROR {ON | OFF}
specifies whether ZLT is enabled or disabled. The default is off. For information about the
ZLT capability, see Chapter 17 (page 309).
REMOTE STANDBY {node-name}
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 309).
{OWNER {owner-id}
where owner-id is either groupname,username or groupnumber,usernumber.
This parameter specifies the userid under which all RDF processes will always run. This
global configuration parameter provides functionality whereby any super-user group userid
can start and stop RDF.
Once the OWNER attribute is set, you must limit EXECUTE access to the RDFCOM object
so that only those super group users authorized to manage RDF can run RDFCOM. Failure
to do so is a serious security risk because, thereafter, all RDF objects run as the userid of the
RDF OWNER.
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 userid, each individual user can be assigned a separate
super-user group userid. If one user is assigned SUPER.FIRST and another SUPER.SECOND,
for example, they can both log on with their userid 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.
By default, this attribute is not set, and therefore is not included in the INFO RDF output.
216 Entering RDFCOM Commands