AutoSYNC Software User's Guide (Update 17)

Command Interpreter
HP AutoSYNC User’s Guide—522580-018
8-23
ADD SYNCFILESET
By default, AutoSYNC compares only modification timestamps of source and
destination SQL tables.
SUBVOLPURGE
instructs AutoSYNC to process subvolumes in the destination file set even if
the subvolumes do not exist on the source file set.
All other synchronization options specified apply to the selection of files to
purge in the destination file set. For example, if the AUDIT option is specified,
the audited files in the extra destination subvolumes are purged.
The REPORT function also lists the extra subvolumes if both PURGE and
SUBVOLPURGE are specified.
SUBVOLPURGE requires the PURGE option. If only PURGE is specified, the
extra subvolumes in the destination file set are not purged.
USEBINDERTIME
selects object files (code 100, 700 and 800 files) for synchronization by
comparing the binder or linker timestamps of the source and destination. For
all other file types in the fileset, the usual modification timestamp is used.
The destination object file is replaced if the binder or linker timestamps of the
source and destination do not match exactly; the comparison operates as if
TIMEEXACT were specified.
The default is that object files are replaced based on a comparison of
modification timestamps.
ZZINC[LUDE]
instructs AutoSYNC to synchronize ZZ* files (saveabend, binder temporary
files, axcel temporary files, so on) and system swap files.
By default, ZZ* files and system swap files are not synchronized.
OSS-only-options
When describing synchronization options for OSS files below, the phrase
"uncontained links" refers to files that are hard links or symbolic links that have
references to files that reside outside of the synchronization file set.
An uncontained hard link is a link to an inode where another link to the same inode
resides outside the synchronization file set.
An uncontained symbolic link points to a file that resides outside the
synchronization file set.
Note. A SQL view or index is synchronized automatically with the primary partition of
the base table. If the redefinition date of an index or view in the source subvolume is
newer than in the destination subvolume but the primary source partition is older than
the primary destination partition, the view or index will not be synchronized.