HP Integrity NonStop H-Series - Manual (Page 84)

Triggers
HP AutoSYNC User’s Guide—522580-021
6-4
Trigger Process File Security
source file modification timestamp and specifying TIMEEXACT will cause the files to
be synchronized needlessly at every synchronization interval.
Trigger Process File Security
If the destination process is remote and the syncuser's process file security has local-
only settings, Autosync upgrades the trigger process file security to network security, to
insure that the trigger can be re-executed successfully at the next synchronization. For
example, if the syncuser’s process file security is set to “AOAO”, AutoSYNC upgrades
it to “NUNU”.
Note that if the remote synchronization process is licensed to perform a "local logon",
the security upgrade is not necessary.
To change the TACL TRIGGER process file security to a setting other than the upgraded
setting, include the following line in the TRIGGER macro text, specifying the desired
setting:
Troubleshooting triggers
For problem resolution and debugging, you can run the trigger command on a terminal
at a TACL prompt.
If the destination is on a remote system, the user must have security privileges
sufficient to run a remote TACL process.
Examples
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:
#set #processfilesecurity "rwep"
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