|
Hi Peter, Basically there are 3 different options, each with their pros and cons. Option 1 - Have file and program in same library Pros - CRTDUPOBJ will not fail adding the trigger when duplicating file into QTEMP (introduced in v5r1). Cons - Does not easily conform to most companies dev/test/prod library structure and methodology. - Trigger program can only be changed when file is not in use. Option 2 - Have file in data library and program in non data library Pros - Easily conforms to most companies dev/test/prod library structure and methodology. Cons - CRTDUPOBJ will fail adding the trigger when duplicating file into QTEMP (introduced in v5r1, this should be going away in v5r4). - Trigger program can only be changed when file is not in use. Option 3 - Have file use middleware that executes application triggers Pros - Easily conforms to most companies dev/test/prod library structure and methodology. - Application trigger program can be changed when file is in use. - CRTDUPOBJ will not fail adding the trigger when duplicating file into QTEMP (introduced in v5r1). Cons - Code will need to be developed/purchased. Hope this helps! Joe Kempenich --- On Fri 02/17, Peter.Colpaert@xxxxxxxxx < Peter.Colpaert@xxxxxxxxx > wrote: From: Peter.Colpaert@xxxxxxxxx [mailto: Peter.Colpaert@xxxxxxxxx] To: midrange-l@xxxxxxxxxxxx Date: Fri, 17 Feb 2006 11:54:04 +0100 Subject: Where to place trigger programs? Hi group, We will start using trigger programs soon (in the testing phase for the moment) to facilitate and automate logging of database changes. I have seen threads on triggers where it is said that it's best to put them in the same library as the data files, and others where this is discouraged. In order to allow us to make a decision, I'd like to hear advantages and disadvantages from either point of view. Thanks in advance, and have a nice weekend (I'm off in 5 minutes ;-) Peter Colpaert Application Developer PLI - IT - Kontich, Belgium ----- Yoda of Borg are we. Futile is resistance, assimilated will you be. -----
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.