HP Integrity NonStop J-Series - Manual (Page 144)

Command Interpreter
HP AutoSYNC User’s Guide—522580-018
8-50
ALTER SYNCFILESET
If RESTORE is omitted, $SYSTEM.SYSnn.RESTORE is used.
SECURE “rwep” | NO SECURE
the security of destination files. If NO SECURE is specified, the security of a
destination file is reset to be the same as that of the source file.
SQLREDEF | NO SQLREDEF
instructs AutoSYNC to synchronize SQL tables based on differences in the
redefinition timestamps, in addition to differences in modified timestamps. This
option allows AutoSYNC to be sensitive to certain DML changes performed on
SQL tables, such as ADD COLUMN, which do not cause the modification
timestamp to change.
The default is NO SQLREDEF.
SUBVOLPURGE | NO SUBVOLPURGE
instructs AutoSYNC to process (or not) 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 | NO 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 file set, 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] | NO ZZINC[LUDE]
instructs AutoSYNC to synchronize ZZ* files (saveabend, binder temporary
files, axcel temporary files, so on) and system swap files.
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.