Owner's manual

Command Interpreter
HP AutoSYNC User’s Guide—522580-015
8-43
ALTER SYNCFILESET
In all cases, the comparison of timestamps accounts for differences in system
clocks and time zones....
TRIGGER { tacl-command | oss-shell-command } | NO TRIGGER
a TACL command or OSS shell command that is executed by AutoSYNC for
each file in the synchronized file set after the file has been moved to the
destination.
The command line contains four built-in arguments. Each argument starts with
a pound sign (#) and is terminated by a TACL delimiter character such as a
space or a comma, or by a OSS shell delimiter such as a space or a
semicolon. Arguments can be specified in either upper or lower case. In the
current release, AUTOSYNC supports the following built-in arguments:
°
#SYNCFILE is replaced with the destination file that has been created or
replaced by AutoSYNC. For OSS files, the absolute pathname is specified.
°
#SOURCEFILE is replaced with the name of the original source file. For
OSS files, the absolute pathname is specified.
°
#RECOVERFILE is replaced with the name of the file that was recovered
by AutoSYNC. If no archive name is found, AUTOSYNC substitutes the
placeholder question mark (?) for the file name. For OSS files, the absolute
pathname is specified.
°
#MAPNAMES is replaced by the mapnames-file that is configured for the
syncfileset using the MAPNAMES option. If the MAPNAMES option is not
specified, AUTOSYNC substitutes the placeholder question mark (?) for
the mapnames-file. This option is applicable to Guardian syncfilesets only.
TRIGGERONFILESET { tacl-command | shell-command }
| NO TRIGGERONFILESET
specifies a tacl or OSS shell command that is executed by AutoSYNC after the
complete file set has been successfully synchronized. This is in contrast with
the TRIGGER option that executes the tacl or shell command for each file that
is synchronized.
Note on symbolic links. Because source and destination modification
timestamps of symbolic links never match, TIMEEXACT is ignored if specified
for symbolic links. For further details on symbolic link synchronization, see
paragraph Modification Timestamp of Symbolic Links on page 5-4
Note on SQL Shorthand Views.
A SQL view has no modification timestamp.
Instead AutoSYNC uses creation timestamps. This prevents a shorthand view
from being synchronized every time the file set is synchronized.
However if TIMEEXACT is specified, the shorthand view will always be
synchronized because the creation time of the destination is always newer
than the creation time of the source. For further details on SQL View
synchronization, see paragraph SQL Views on page 3-7.