HP NonStop G-Series - Manual (Page 197)

Command Interpreter
HP AutoSYNC User’s Guide—522580-016
8-105
SYNCHRONIZE
KEEPNOPURGEUNTIL is not supported for Enscribe files, consistent with
FUP and RESTORE behavior.
MAPNAMES mapnames-file
specifies the mapping of a source fileset to a destination fileset and catalog
name mapping.
The mapnames-file is an edit or entry-sequenced file located on the destination
system.
File name mapping:
The mapnames-file entries are similar to, but not exactly the same as, the
MAP NAMES option of RESTORE. Each line of the MAPNAMES file
contains a single mapping of the form.
The file name can be partially qualified; AutoSYNC replaces the missing
portion of the name with the wild card asterisk (*). For example:
Are equivalent to:
Catalog name mapping:
The information in MAPNAMES is also used to perform SQL catalog
volume mapping. You should include MAPNAME entries if catalogs are
located on different volumes or subvolumes on the destination system.
The entries follow file mapping entries and are preceded by the keyword
"CATALOGS:", including the colon (:), as follows:
CATALOGS entries are checked for proper syntax, and passed along to
the RESTORE process.
See discussion on the use of MAPNAMES in Alternate Key Files on page 3-6,
SQL Tables and Catalogs on page 3-7, Partitioned Files and Tables on
source-file-pattern TO destination-file-pattern
$DATA TO $BACK
\NEWYORK.$DATA*.DB TO $BACK.BACKUPDB
$DATA*.DB.PARTFILE TO \TOKYO.*
\SOURCE.$DATA.*.* TO \DEST.$BACK.*.*
\NEWYORK.$DATA*.DB.* TO \DEST.$BACK.BACKUPDB.*
\SOURCE.$DATA*.DB.PARTFILE TO \TOKYO.*.*.*
$DATA TO $BACK
\NEWYORK.$DATA*.DB TO $BACK.BACKUPDB
$DATA*.DB.PARTFILE TO \TOKYO.*
CATALOGS:
$CATS.BACKCAT FOR $BACK.*.*
$CATS.DBCAT FOR $BACK.BACKUPDB.*
\TOKYO.$CATS.DBCAT for \TOKYO.*.*.*