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

INCLUDEPURGE and EXCLUDEPURGE
These updater attributes work exactly the same as for INCLUDE and EXCLUDE, with the exact same
wildcard functionality, and with the exact same performance ramifications.
There is one additional consideration. The total number of INCLUDE, EXCLUDE, INCLUDEPURGE,
and EXCLUDEPURGE clauses that you can have for one updater is 100. This means, for example,
that you can have 25 for each of the these clauses, but not one more. If you have 50 INCLUDEs
and 50 EXCLUDEs, then you cannot add any INCLUDEPURGE and EXCLUDEPURGE clauses for
the updater. Please note that the aggregate for the updater is 100 for all four types. If you have
no INCLUDEs and no EXCLUDEs, then you can have up to 100 INCLUDEPURGE and
EXCLUDEPURGE clauses - for example 80 INCLUDEPURGE and 20 EXCLUDEPURGE clauses.
Alternatively, you could have 100 EXCLUDEPURGE clauses, but note that in this case you cannot
have any INCLUDE, EXCLUDE, and EXCLUDEPURGE clauses.
Observe the following example.
SET VOLUME CPUS 1:2
SET VOLUME IMAGEVOLUME $IMAGE
SET VOLUME PRIORITY 185
SET VOLUME PROCESS $MM01
SET VOLUME UPDATEVOLUME $DATA01
SET VOLUME INCLUDE MMTEST10.*
SET VOLUME INCLUDEPURGE MMTEST.FILE*
SET VOLUME EXCLUDEPURGE MMTEST.FILE10
ADD VOLUME $DATA01
In the example, the INCLUDE clause specifies that only audited files in $DATA01.MMTEST10 are
to be replicated. The INCLUDEPURGE clause specifies that every Enscribe purge operation involving
files in this same subvolume are to be replicated, but the EXCLUDEPURGE clause specifies that any
purge operations involving the file $DATA01.MMTEST10.FILE10 are NOT to be replicated.
Error Checking
Extensive checking is done when the subvolume and file names are parsed, and invalid names
cause errors. The logic of a series of INCLUDE and EXCLUDE clauses, however, is not checked.
For example, information is not regarded as an error, even though it makes no sense because
everything will be filtered out:
SET VOLUME INCLUDE MMTEST10.*
SET VOLUME EXCLUDE MMTEST10.*
Performance Ramifications
The extractor processes all INCLUDE and EXCLUDE clauses. If the extractor reads an audit record
associated with a file or table not specified in an INCLUDE clause, it discards the record. Similarly,
if the extractor reads an audit record associated with a file or table specified in an EXCLUDE
clause, it discards the record.
With volume-level replication, the extractor needs to test only the volume name to determine if a
record should be sent to the backup system. With subvolume- and file-level replication, however,
the extractor must also test the subvolume name and filename. Hence there is more work to do
with subvolume- and file-level replication. If you use large numbers of INCLUDE and EXCLUDE
clauses for each volume, the extractor might have to evaluate the subvolume name and filename
against multiple lists, which could lead to increased CPU usage by the extractor and lower extractor
performance than with simple volume-level replication. Therefore, you should be careful about how
many INCLUDE and EXCLUDE clauses you specify for each volume. The use of wildcard characters
in subvolume names and filenames can help considerably. For example, to replicate all of the files
within all subvolumes whose names begin with the letters DB, you can do so with a single INCLUDE
clause:
INCLUDE DB*.*
274 Subvolume-Level and File-Level Replication