AutoSYNC Software User's Guide (Update 19)

Command Interpreter
HP AutoSYNC User’s Guide—522580-020
8-44
ALTER SYNCFILESET
The time elapsed is computed from the last time the file was modified. The
candidate files can be opened for WRITE or READ-WRITE access. The
exclusion mode must be SHARED or PROTECTED. Recovery must be
enabled for the file set.
If a file is being updated at the time AutoSYNC attempts to synchronize it, it is
skipped. To force the synchronization of a file as it is being modified, specify
the UNPROTECTED option described below on page 8-48.
OPENUPDATE is ignored if:

a file is opened for EXCLUSIVE access

for Guardian file sets only:

if a file is audited

if the global SYNCRECOVER parameter is set to OFF or if NO
RECOVERY was specified when the file set was created or altered.
OWNER [ user-id | user-name ] | NO OWNER
the owner of the destination file set.
If OWNER is omitted, the owner of the source file is retained.
PRI[ORITY] priority | NO PRI[ORITY]
the process priority at which the ASYSYNC process is to run when processing
this syncfileset.
If priority exceeds the value of MAXPRIORITY set with the ADD SYNCUSER
or ALTER SYNCUSER command, it is overridden by the syncuser's
MAXPRIORITY.
If this option is omitted, the priority of ASYSYNC is set to the priority of the
syncuser.
PURGE | NO PURGE
Note for OSS file sets. AutoSYNC only synchronizes updates that are actually sent
to the disk process. Any updates that are buffered in the application process (such as
performed by the file system or C runtime) are not synchronized until they are
transmitted to the disk process.
Note for OSS file sets. If OWNER is specified and OWNERGROUP is omitted, the
OWNERGROUP of the file set is set to the group of the source file, not the group
specified by OWNER.
Note. Be aware that running ASYSYNC at high priority may impact system
performance as the process is CPU bound.