AutoSYNC Software User's Guide (Update 19)

Command Interpreter
HP AutoSYNC User’s Guide522580-020
8-15
ADD SYNCFILESET
the owner of the destination file set.
If OWNER is omitted, the owner of the source file is retained.
PRI[ORITY] priority
the process priority at which the ASYSYNC process is to run when processing
this syncfileset.
If the priority exceeds the value of MAXPRIORITY set with the ADD
SYNCUSER or ALTER SYNCUSER command, it is overridden by the
syncuser's MAXPRIORITY.
If this option is omitted, the priority of ASYSYNC is set to the priority of the
syncuser.
PURGE
specifies that any file that is in the destination file set but is not in the source
file set will be purged. By default AutoSYNC does not purge any file in the
destination file set.
To exclude files from being purged on the destination, use the
EXCLUDEPURGE option.
Guardian file sets:
If PURGE is specified, the subvolume portion of the source and destination
file sets must be fully qualified (no wild-card characters or "*").
Purging of files occurs on a subvolume by subvolume basis. A destination
file is not purged if it does not exist in a corresponding source subvolume,
unless the SUBVOLPURGE option is also specified.
Extra SQL objects in the destination like tables, views and indexes are
purged. Catalog files are not supported and they are not synchronized or
purged by Autosync.
Extra SQL tables and views are purged explicitly, indexes and secondary
partitions are purged implicitly, with the main table.
OSS system files named $*.ZYQ*.* are automatically excluded from being
purged on the destination system.
SYSDB and MapDB subvolumes are automatically excluded from
being purged on the destination subvolume.
Note for OSS file sets. If OWNER is specified and OWNERGROUP is omitted, the
OWNERGROUP of the file set is set to the group of the source file, not the group
specified by OWNER.
Note. Be aware that running ASYSYNC at high priority may impact system
performance as the process is CPU bound.