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

Furthermore, RDF objects with a particular ATINDEX value greater than 0 must together constitute
a complete set:
• If there is an extractor with an ATINDEX value of 1, there must also be a receiver with an
ATINDEX value of 1.
• If there is a receiver with an ATINDEX value of 1, there must also be a secondary image trail
with an ATINDEX of 1.
• An updater with an ATINDEX value of 1 must be protecting a primary system data volume
configured to auxiliary audit trail AUX01, and its secondary image trail must also have an
ATINDEX value of 1.
Once an updater process has been added to the RDF configuration, you cannot alter its INCLUDE
or EXCLUDE parameters. If you must do so, you have to delete the updater and then add it back
to the configuration as described in Chapter 11 (page 261).
You can specify a maximum of 100 INCLUDE and EXCLUDE parameters for each volume, in
any combination.
Unlike the behavior of other SET parameters, successive INCLUDE or EXCLUDE parameters
do not supersede preceding ones in the RDF configuration memory table (they merely extend
the include and exclude lists for the particular data volume).
As with SET parameters for all RDF object types, specified INCLUDE and EXCLUDE parameters
remain in the RDF configuration memory table even after you add the updater to the configuration.
This can be useful, for example, if the same INCLUDE and EXCLUDE parameters apply to
multiple volumes. If the parameters vary from one volume to the next, however, you must
remember to issue a RESET VOLUME command after adding each updater (otherwise the
INCLUDE and EXCLUDE parameters for each added updater are applied to the next added
updater as well).
To view the current INCLUDE and EXCLUDE parameters in the RDF configuration memory
table, issue a SHOW VOLUME command.
To view the INCLUDE and EXCLUDE parameters for an updater that has already been added,
issue an INFO VOLUME or INFO $volume command.
Examples
Suppose that one of the volumes containing audited files on the primary system is named
$DATA01 and you want to create an updater process named $U01 to maintain a copy of that
volume, named $DATA1, on the backup system.
To configure the updater process to run in CPUs 3 and 4 at the default priority of 160 using the
secondary image trail volume $SECIT1, issue these commands:
]SET VOLUME PROCESS $U01
]SET VOLUME CPUS 3:4
]SET VOLUME IMAGEVOLUME $SECIT1
]SET VOLUME UPDATEVOLUME $DATA1
]ADD VOLUME $DATA01
To configure the updater process to run in CPUs 3 and 4 at the default priority of 160 using the
secondary image trail volume $SECIT1, and having the mapfile $DATA05.CONFIG.MAPFILE
and the maplog $DATA05.LOG.MAPLOG, issue these commands:
]SET VOLUME PROCESS $U01
]SET VOLUME CPUS 3:4
]SET VOLUME IMAGEVOLUME $SECIT1
]SET VOLUME UPDATEVOLUME $DATA1
]SET VOLUME MAPFILE $DATA05.CONFIG.MAPFILE
]SET VOLUME MAPLOG $DATA05.LOG.MAPLOG
]ADD VOLUME $DATA01
224 Entering RDFCOM Commands