Re: Difference between trigger types -- MIDRANGE-L

Have you looked at the Redbook that discusses triggers? It also talksabout stored procedures and user-defined functions. It might havethis kind of info, or at least give you enough of the characteristicsof each, to be able to make a reasoned choice. The chapter on SQLtriggers says that the main benefit of them is portability.


http://www.redbooks.ibm.com/redbooks/pdfs/sg246503.pdf

You might look at www.iseries.ibm.com/db2 and dig around - there is acourse about modernizing by using SQL, with some justification stuff, I think.


HTH

At 03:39 PM 12/3/2006, you wrote:

I've been trying to work out the difference between triggers implemented
via SQL and triggers implemented through the ADDPFTRG command.



I've been using both types, but haven't been ale to find any
documentation on which was one is more appropriate in particular
circumstances.



I often use SQL triggers to trap obscure bugs which place erroneous data
in the data base. I found some code some time ago which enabled me to
trap the data condition in the SQL trigger code and pass a bunch of
values to an SQL procedure which then invoked a CL program and passing
it values obtained from the 'new row' row.



I've also recently added a trigger via ADDPFTRG to trigger the
generation of an e-mail when a record was inserted into a file. This
trigger simply invokes the CL program but doesn't pass any values across
because ADDPFTRG doesn't allow this. From other reading it appears that
a trigger buffer is available to obtain information in lieu of
parameters. It appear that an RPG trigger program would be best in this
circumstance.



I'm trying to make sense of all the options available and was wondering
if there is a simple article which covers the issues I've raised above.



Thanks again.


*********************************************************************************************************

This email and any files transmitted with it are confidential andintended solely for the use of the individual or entity to whom theyare addressed. If you are not the intended recipient, any use,disclosure or copying of this message is unauthorised. If you havereceived this message in error, please reply using the sender's email address.

This footnote confirms that this email message has been scanned forcomputer viruses. EIG-Ansvar Limited does not accept liability forany loss or damage, whether caused by our own negligence or not,that results from a computer virus or defect in the transmission ofthis email or any attached file.


EIG-Ansvar Limited - Australia (A.B.N. 21 007 216 506)
Email : insure@xxxxxxxxxxxxxxxx

Eig-Ansvar Limited - New Zealand
Email : insure@xxxxxxxxxxxxxxxx

*********************************************************************************************************
--
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.