AutoSYNC Software User's Guide (Update 19)
Command Interpreter
HP AutoSYNC User’s Guide—522580-020
8-114
SYNCHRONIZE
RENAMEO[PEN]
specifies that destination unaudited files that are opened for shared READ 
access or running object files are to be renamed to allow AutoSYNC to replace 
them.
The syncuser must have PURGE privileges to the destination file for the 
RENAME to succeed.
Both the old and new file names are recorded in an AutoSYNC index file called 
AAINDEX, located in the MapDB subvolume.
The renamed files are named AAnnnnnn, where nnnnnn is a sequence 
number, and are placed in the same subvolume name as the AutoSYNC 
MapDB, in the destination file set volume. Renamed partitions, alternate 
indexes and protection views are named ABnnnnnn, ACnnnnnn, and so on.
RESTORE restore-program
the name of the RESTORE object program to use on the destination system 
when a file set is synchronized.
If RESTORE is omitted, $SYSTEM.SYSnn.RESTORE is used.
SECURE “rwep”
the security of destination files. If this option is omitted, the security of a 
destination file is the same as that of the source file.
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.
By default, AutoSYNC compares only modification timestamps of source and 
destination SQL tables.
SUBVOLPURGE
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.










