AutoSYNC Software User's Guide (Update 17)

Triggers
HP AutoSYNC User’s Guide522580-018
6-3
TRIGGERONFILESET
If no archive name is found, AutoSYNC will pass the placeholder question mark
(?). For OSS, files the absolute pathname is specified.
Recovery files have a name chosen by AutoSYNC. Such files are usually purged
by AutoSYNC when the replacement file has been synchronized, but triggers may
preserve these files by renaming them
#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
TRIGGERONFILESET Arguments
#SOURCEFSET is replaced with the original source file set name.
#DESTFSET is replaced with the designating file set name.
#FSETCOUNT is the number of files in the source file set.
#SYNCCOUNT is the number of files replaced on the destination.
#COUNTNOTBKUP is the number of files not backed up.
#COUNTNOTREST is the number of files that were not restored.
Trigger Output
The TACL trigger command and the output of the TACL or OSS session are captured
in the log file:
For scheduled synchronizations, the log file is the MapDB file SLggguuu.
For a one-time synchronization, the user specifies the LOGFILE option in the
SYNCHRONIZE command.
If your triggers generate a lot of output, consider sending the output to a dedicated
trigger log file, which would be specified in the trigger macro.
You can also simply increase the size of the AutoSYNC log file, as instructed in
paragraph Managing the SLggguuu Log File on page A-2. Consider however that a
large volume of trigger output in the AutoSYNC log might clutter the file and make it
more difficult to peruse for problem resolution.
Triggers and TIMEEXACT
If you configure a syncfileset that invokes a trigger to modify some of the files that were
replaced on the destination, avoid using the TIMEEXACT option. If files are modified
by a trigger command, their last modified timestamp is always more recent than the