Owner's manual

Triggers
HP AutoSYNC User’s Guide—522580-015
6-3
Trigger Examples
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.
Troubleshooting triggers
For problem resolution and debugging, you can run the trigger command on a terminal
at a TACL prompt.
The user must have security privileges sufficient to run a remote TACL process.
Trigger Examples
1. SQL-compile the synchronized object file myslqprg.
SQLCOMP is invoked in the TACL macro sqlcmpme that sets up the defines for
the compilation:
2. Change the node name \sys1 to \sys2 in a synchronized edit file nodename:
Note. 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, or simply increase the size of the
AutoSYNC log file, as instructed in paragraph Managing the SLggguuu Log File
on page A-2.
SYNC trigtest.mysqlprg TO \sys2.$data.trigtest.*,
TRIGGER "sqlcmpme #syncfile", LOGFILE synctest.log;
Where sqlcmpme uses obey file mydefine before launching SQLCOMP:
?tacl macro
#frame
#push :file
#set :file %1%
system \sys02
obey mydefine
sqlcomp /in [:file], out $s.#sqlcomp/catalog \sys2.vol.subvol, explain,
currentdefines
#unframe
SYNC trigtest.nodename TO \sys2.$data.trigtest.*, LISTALL,
TRIGGER "edit /in trigin.updatsys/#SYNCFILE",LOGFILE synctest.log;
Where trigin.updatsys is:
cab/sys1/sys2/a;la