RE: Where to place trigger programs?

All our programs (trigger and otherwise) are in a separate library from the
data (mainly because we have multiple databases). I have a utility I wrote
which (when run under the correct library list) determines the trigger
program's library and adds the triggers using that explicit library. We use
Softlanding's Turnover, and I have it looking at Turnover's explode list to
make sure the triggers are applied to the file in all the data libraries.
Plus, my trigger program shell uses the EXTFILE keyword on the audit file's
F-spec to make sure I write to the audit file in the correct library.

Francis Lapeyre
IS Dept. Programmer/Analyst
Stewart Enterprises, Inc.
E-mail: flapeyre@xxxxxxxx 



-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Fleming, Greg (ED)
Sent: Friday, February 17, 2006 7:12 AM
To: Midrange Systems Technical Discussion
Subject: RE: Where to place trigger programs?



|The only problem with placing the trigger is that both the file and the 
|trigger program need to be in the library list any time data in the 
|file is touched.

I think this would only be true if you specified *LIBL as the library for
the trigger program on the ADDPFTRG command.  

We specify the library name of the trigger program on our triggers, so the
library list of the user or job updating the file won't matter.  

Greg Fleming

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at http://archive.midrange.com/midrange-l.