AutoSYNC Software User's Guide (Update 20)

One-time Synchronization
HP AutoSYNC User’s Guide—522580-021
3-20
Keeping NOPURGEUNTIL Attribute

Only a file’s local owner, local group manager, or the local Super user can set the
PROGID attribute.
No remote user, even the Super user, can set the LICENSE or PROGID attributes.
If you synchronize a LICENSEd or PROGIDed object file to a destination on the same
system, the attributes are preserved if you have the authority to set those attributes in
the first place. You must be the Super user to preserve the LICENSE attribute; you
must be the file owner (or the owner’s manager or the Super user) to preserve the
PROGID attribute.
If you synchronize such an object file to a remote destination, the file is moved, but
those attributes are removed. AutoSYNC issues a warning message for each file that
has its attributes removed.
To synchronize object files to a remote destination, and preserve the LICENSE and
PROGID attributes, you must:
1. Use an appropriate user ID
2. License the destination ASYSYNC (or the ASYSYNCP if synchronizing over
TCP/IP) as described in Licensing Synchronization Processes on page 2-11.
As a local process, the synchronization process can set LICENSE and PROGID
attributes if the proper user ID is used.
Keeping NOPURGEUNTIL Attribute
The NOPURGEUNTIL attribute on a file or a table specifies the earliest date where the
file can be purged.
By default, AutoSYNC does not propagate the NOPURGEUNTIL attribute to the
destination, to insure that future synchronizations of the file or table will be possible.
To retain the NOPURGEUNTIL attribute for a SQL table or alternate index on the
destination, specify the KEEPNOPURGEUNTIL option. Subsequent synchronization
attempts will fail until the NOPURGEUNTIL period has elapsed.
KEEPNOPURGEUNTIL is not supported for Enscribe files, to remain consistent with
the behavior of FUP and RESTORE. FUP and RESTORE do not propagate the
NOPURGEUNTIL attribute for Enscribe files.
Preserving Other Security Attributes
You can also replace destination files even if you have elected to keep local purge
access to the files. To keep the PURGE security of a file on the destination system as
“O” or “G” for example, you will need to license the ASYSYNC or ASYSYNCP (if
synchronizing over TCP/IP) to allow it to run as a local process, as described in
Licensing Synchronization Processes on page 2-11.