HP NonStop G-Series - Manual (Page 136)

Command Interpreter
HP AutoSYNC User’s Guide—522580-015
8-48
ALTER SYNCFILESET
in the destination fileset volume. Renamed partitions, alternate indexes and
protection views are named ABnnnnnn, ACnnnnnn, and so on.
RESTORE restore-program | NO RESTORE
the name of the RESTORE object program to use on the destination system
when a file set is synchronized.
This option overrides the RESTORE option specified in the ADD SYNCUSER
or ALTER SYNCUSER command.
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.
Note. If the destination file is audited, AutoSYNC displays a warning message and
the file is not synchronized. An audited file cannot be renamed and AutoSYNC cannot
temporarily unaudit the file to rename it because the file is opened.
Note. A synchronized file, table, index or view may not replace an existing object of a
different type.
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.