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

Example
To configure the primary system \RDF04 and backup system \RDF06, issue the following commands
after RDF has been initialized:
SET NETWORK PRIMARYSYSTEM \RDF04
SET NETWORK BACKUPSYSTEM \RDF06
SET NETWORK REMOTECONTROLSUBVOLUME RDF04
SET NETWORK PNETTXVOLUME $DATA07
ADD NETWORK
SET PURGER
The SET PURGER command sets purger process 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 PURGER command.
SET PURGER purger-option
where purger-option is:
{CPUS primary-CPU : backup-CPU }
{PRIORITY priority }
{PROCESS process-name }
{PURGETIME mins }
{RETAINCOUNT num }
CPUS primary-CPU : backup-CPU
identifies the CPUs in which the purger process is to run as a process pair on the backup system;
primary-CPU is the primary CPU; backup-CPU is the backup CPU. Values range from 0
through 15. The default is 0:1.
PRIORITY priority
identifies the execution priority for the purger process; priority is the execution priority,
from 10 through 199. The default is 165.
PROCESS process-name
specifies the process name for the purger process; process-name is any unique, valid process
name of up to six characters; the first character must be a dollar sign ($). You cannot specify
any of the reserved process names listed in the Guardian Procedure Calls Reference Manual.
This parameter is not optional. You must explicitly name the purger process.
PURGETIME mins
specifies the number of minutes the purger process waits between attempts to purge redundant
image trail files. The default value is 60 minutes.
RETAINCOUNT num
specifies how many image trail files must be retained on disk for each image trail (including
the image trail file currently in use). num must be within the range 2 to 5000. If you do not
explicitly set this configuration parameter, the default value is 2. This configuration parameter
is only relevant for the triple contingency feature; otherwise, this parameter should be left at
its default value.
This parameter is important because if you lose the primary system, the triple contingency protocol
will work only if all of the missing audit records at the backup system which is further behind in its
RDF processing is still on disk on the other backup system.
For example, assume that you have lost the original primary system (\A), you have successfully
completed a takeover on both backup systems (\B and \C), and the MAT positions displayed by
the respective 735 messages are:
\B: 735 LAST MAT POSITION: Sno 10, RBA 100500000
\C: 735 LAST MAT POSITION: Sno 10, RBA 100000000
500 kilobytes of audit records is missing on \C.
RDFCOM Commands 215