AutoSYNC Software User's Guide (Update 17)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-018
3-17
Changing File Security
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

If a file is owned by a user ID different than the user performing the
synchronization, the Purge security is set to allow the user that performs the
synchronization to purge the file.

If a file is copied to a remote destination, the security of the replicated file is altered
to allow remote access.
If a file with a local security “A”, “G”, or “O” is synchronized to a remote destination
system, you might not be able to access this file remotely, so AutoSYNC automatically
alters the security to “N”, “C”, or “U”, respectively. To retain the original security of the
synchronized files, use the NO NETWORKSECURE option.
You may also specify that all files transferred to the destination have a specific security
by using the SECURE option. In order to preserve the ability to do future
synchronizations, PURGE security cannot be changed through the SECURE option
(see Default PURGE Security above).
SAFEGUARD security is transferred with the file. VOLUME and SUBVOLUME
protection are not transferred but can be set prior to synchronization and before any
files exist in the destination location. Adding DISKFILE protection requires the file to
exist; the PERSISTENT ON attribute retains the SAFEGUARD file-protection record
after the file is purged.
Compression
To reduce the amount of data that is transferred between the source and a remote
destination, AutoSYNC can compress the data. The LZW compression algorithm
typically eliminates 50 percent to 60 percent of the volume of the data.
The use of data compression requires more cpu time on the source and destination
systems, but reduces usage of the transport medium. By default, AutoSYNC does not
use compression because in most configurations compression does not enhance
throughput. In most environments, the increase in CPU usage outweighs the savings in
data volume.