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

]SET PURGER PROCESS $PRG
]SET PURGER CPUS 0:1
]SET PURGER RETAINCOUNT 8
]ADD PURGER
By default, in this example the purger process will run at a priority of 165 and the purger purgetime
is set to 60 minutes.
SET RDF
The SET RDF command sets RDF global configuration parameters within the RDF configuration
memory table. The supplied values are not applied to the RDF configuration file, however, until
you issue an ADD RDF command.
SET RDF global-option
where global-option is:
{LOGFILE $ems-collector-name }
{UPDATERDELAY delay-time }
{UPDATERTXTIME tx-time }
{UPDATERRTDWARNING rtd-time }
{UPDATEROPEN {PROTECTED | PROTECTED OPEN | SHARED} }
{SOFTWARELOC $volume.subvolume }
{NETWORK {ON | OFF} }
{NETWORKMASTER {ON | OFF} }
{UPDATEREXCEPTION {ON | OFF} }
{LOCKSTEPVOL $volume }
{REPLICATEPURGE {ON | OFF} }
{REMOTE MIRROR {ON | OFF} }
{REMOTE STANDBY {node-name} }
{OWNER {owner-id} }
LOGFILE ems-collector-name
specifies a device (EMS collector) that is to receive messages from RDF. The specified device
must exist on both the primary and backup systems. The default is $0.
The device on the primary system receives log messages from the extractor and monitor
processes plus RDFCOM messages that are logged in message 835 and messages from
RDFNET, if configured.
The device on the backup system receives log messages from the receiver, purger, and all
updater processes (plus RDFCOM messages that are logged in message 835).
UPDATERDELAY delay
specifies how many seconds (from 1 to 10) the updater processes should delay upon reaching
the logical EOF in the image trail before attempting a new read. The default is 10 seconds.
The default updater delay is the recommended value for virtually all users of RDF. Lowering it
could adversely affect other updaters’ performance.
You can alter the UPDATERDELAY value while updaters are running by using the ALTER RDF
UPDATERDELAY command.
UPDATERTXTIME tx-time
specifies the maximum transaction duration (in seconds, from 10 to 300) for all updater
processes. The default is 60 seconds.
RDF updaters operate in transaction mode. Updater transactions are essentially long-running
transactions that pin audit trail files on the backup system and can affect the duration of backout
operations if an updater transaction aborts for any reason.
The default value is recommended for RDF environments with heavy updater activity (aggregate
updater throughput greater than 300 kb/second). Raising the tx-time in such environments
could adversely affect TMF performance on the backup system.
RDFCOM Commands 217