RDF System Management Manual

Entering RDFCOM Commands
HP NonStop RDF System Management Manual—524388-003
8-70
Command Overview
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 Section 14, Process-Lockstep Operation.
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 Section 16, Zero Lost Transactions (ZLT).
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 Section 16, Zero Lost Transactions (ZLT).
{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