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

To illustrate this problem scenario, assume these circumstances:
• You create an audited, partitioned, key-sequenced file (Enscribe, SQL/MP, or SQL/MX) on
the primary system where the primary and secondary partitions are on the same subvolume
at $DATA01.SVOL.FILE and $DATA02.SVOL.FILE.
• One updater replicates the changes for the primary partition $DATA01.SVOL.FILE on the
primary system to $DATA11.SVOL1.FILE on the backup system using this mapping string:
MAP NAMES SVOL.* TO SVOL1.*
• A second updater replicates the changes for the secondary partition $DATA02.SVOL.FILE
on the primary system to $DATA22.SVOL2.FILE on the backup system by using this mapping
string:MAP NAMES SVOL.* TO SVOL2.*
As a result of these mapping rules, both partitions on the backup system are created in the same
subvolume, SVOL1. When the second updater applies an audit to the secondary partition,
$DATA22.SVOL2.FILE, it reports an error 11 because the partition $DATA22.SVOL2.FILE does
not exist.
If you run FUP COPY on the primary partition file $DATA02.SVOL1.FILE on the backup system,
FUP reports file-system error 3 or 72 when it attempts to open the secondary partition file
$DATA22.SVOL2.FILE. FUP displays the contents of the primary partition file but not the contents
of the secondary partition file.
To avoid this problem, when you map a subvolume on the primary system to a differently named
subvolume on the backup system, always ensure that the mapping rules do not affect partitioned
files.
Managing Subvolume Name Mapping for Partitioned Files 269