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

In this example, changes to all audited files and tables on $DATA01 are replicated, except
MMTEST10.CONC0826:
SET VOLUME CPUS 1:2
SET VOLUME IMAGEVOLUME $IMAGE
SET VOLUME PRIORITY 185
SET VOLUME PROCESS $MM01
SET VOLUME UPDATEVOLUME $DATA01
SET VOLUME EXCLUDE MMTEST10.CONC0826
ADD VOLUME $DATA01
Wildcard Character (*)
The asterisk (*) can be used as a wildcard character in both subvolume and file names.
Within Subvolume Names
When used to designate subvolume names, the * must always be used as a suffix.
su*v.fname, *.fname, and *.*, for example, are not valid.
But DB*.filename is valid because the asterisk is used as a subvolume name suffix. In this case,
changes made to all audited files and tables on all subvolumes whose name starts with DB on the
protected data volume are replicated.
Within Filenames
When used by itself as a filename, the * designates all audited files and tables on the specified
subvolume. When used as a suffix, the * designates all audited files and tables on the specified
subvolume whose names start with the supplied pattern. If the * is not used by itself to represent
all files, it must be used as a suffix. Embedded wildcard characters (such as fil*nam) are not
valid.
NOTE: You can use ALTER VOLUME to modify the INCLUDE and EXCLUDE clauses when RDF
is running. This command supports only files for inclusion or exclusion. Wild cards within files
names and subvolume names are not supported by this command. For more details on this command,
see “ALTER” (page 183).
INCLUDE/EXCLUDE and RDFCOM In-Memory Table
Recall that when you use the SET commands to set various attributes of an RDF object, the set
commands store the values you set in an in-memory table. If you use INCLUDE and/or EXCLUDE
lists when you configure an updater, these are also stored in the in-memory table too. This can
make using the same INCLUDE and EXCLUDE lists for each volume very convenient because you
only have to specify them for the first volume and they are carried over to each subsequent volume
that you add for RDF protection. For example, consider the following:
SET VOLUME CPUS 1:2
SET VOLUME IMAGEVOLUME $IMAGE
SET VOLUME PRIORITY 185
SET VOLUME PROCESS $MM01
SET VOLUME UPDATEVOLUME $DATA01
SET VOLUME INCLUDE MYSUBVOL.MYFILE
SET VOLUME INCLUDE MMTEST10.FILE1
SET VOLUME INCLUDE MMTEST10.FILE2
ADD VOLUME $DATA01
SET VOLUME CPUS 1:2
SET VOLUME IMAGEVOLUME $IMAGE
SET VOLUME PRIORITY 185
SET VOLUME PROCESS $MM02
SET VOLUME UPDATEVOLUME $DATA02
ADD VOLUME $DATA01
272 Subvolume-Level and File-Level Replication