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

In the above 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*.*
Replicating purge operations with INCLUDE, EXCLUDE, INCLUDEPURGE,
and EXCLUDEPURGE lists
You can combine INCLUDE, EXCLUDE, INCLUDEPURGE, and EXCLUDEPURGE settings for a
volume. The RDF extractor decides the effect of these clauses on a purge operation (file/fileset) for
an RDF protected volume.
Table 16 lists the possible combinations and the effect of combining the clauses.
NOTE: Only logical combinations that are frequently used are listed. The combinations and their
effect are based on the assumption that the REPLICATEPURGE parameter is ON.
Table 16 Replicating purge operations with INCLUDE, EXCLUDE, INCLUDEPURGE, and EXCLUDEPURGE
Purge Operation ProcessingEXCLUDEPURGEINCLUDEPURGEEXCLUDEINCLUDE
All purge operations are replicated.Not DefinedNot DefinedNot DefinedNot Defined
The RDF extractor checks if INCLUDE list has
the file/fileset. If yes, the purge operation is
not filtered.
Not DefinedNot DefinedDefinedDefined
Error Checking 269