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

One-time Synchronization
HP AutoSYNC User’s Guide—522580-017
3-16
Synchronizing based on REDEFINITION timestamp
Synchronizing based on REDEFINITION timestamp
By default, AutoSYNC compares source and destination MODIFICATION timestamps
to decide if the destination table needs to be replaced.
Users might want to synchronize tables after performing certain types of DML
operations on SQL tables, such as adding a column or a partition or creating an index.
However these operations leave the MODIFICATION timestamp unchanged and
update only the REDEFINITION timestamp, causing AutoSYNC to overlook the
change that occurred on the table.
To synchronize tables based on differences in the REDEFINITION timestamp, use the
SQLREDEF option. AutoSYNC then compares the source and destination
REDEFINITION timestamps of the table, in addition to the MODIFICATION
timestamps, to decide if a table requires synchronization.
Note that a SQL index is synchronized automatically with the primary partition of the
base table. If the redefinition date of an index in the source subvolume is newer than in
the destination subvolume, but the primary source partition is older than the primary
destination partition, the index will not be synchronized.
Synchronizing based on Binder or Linker timestamp
Certain operations performed on an object file cause the MODIFICATION timestamp of
the file to change but do not alter the file in ways that require synchronization. For
example, SQL compiling a program on the source system changes the modification
timestamp of the object file but does not require the replacement of the file on the
destination. This is reflected by the fact that the binder or linker timestamp of the object
file is unchanged by the SQLCOMP utility.
By default however, AutoSYNC always replaces an object file that has been SQL
compiled on the source after it was last synchronized, because it compares source and
destination MODIFICATION timestamps and they will always be different after the
source has been SQL compiled.
To avoid replacing object files that have not changed, configure AutoSYNC to compare
source and destination binder or linker timestamps instead of comparing
MODIFICATION timestamps by specifying the USEBINDERTIME option. The
destination object file is replaced only if the binder or linker timestamps of the source
and destination do not match exactly; the comparison operates as if TIMEEXACT were
specified.
The option is applicable to object files only (code 100, 700 or 800 files) and is ignored
for all other file types.
Changing File Security
By default, the security of each synchronized file is preserved, except that