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

trail on the mirrored volume now plugged into the standby system to the receiver on the backup
system.
LOCKSTEP control-subvol, REMOTESYS standby-node
control-subvol
specifies the name of the RDF control subvolume on the backup system that requires the
LOCKSTEP and subsequent TAKEOVER commands.
standby-node
specifies the name of the standby system where the audit-trail mirror has been brought online.
Where Issued
Backup system only.
Security Restrictions
You can issue the LOCKSTEP command only if you are a member of the super-user group.
RDF State Requirement
You can issue the LOCKSTEP command only if the communication lines between the backup
and primary systems are down, or the monitor process is not running on the primary system.
Usage Guidelines
The LOCKSTEP command is for use only in conjunction with a TAKEOVER command under
very specific circumstances. Issue this command only if your RDF environment has been
specifically configured for lockstep protection and you have read all of the applicable text in
Chapter 11 (page 261).
Example
In an RDF environment configured for standby takeover protection, assume that \STANDBY is
the name of the standby system and RDF1 is the name of the RDF control subvolume on the
backup system.
The following LOCKSTEP command starts an extractor on the standby system, and that extractor
sends audit data from the audit trail on the mirrored volume now plugged into the standby
system to the receiver on the backup system:
]LOCKSTEP RDF1, REMOTESYS \STANDBY
OBEY
The OBEY command executes a series of commands entered in a command file.
OBEY [\system.][$volume.][subvolume.]file
system
identifies the system on which the command file is stored.
volume
identifies the disk volume on which the command file is stored.
subvolume
identifies the subvolume on which the command file is stored.
file
identifies the command file, which contains one or more valid RDFCOM commands.
Where Issued
Primary or backup system.
RDFCOM Commands 203