|
At 10:37 08/21/2001, David Morris wrote: >you can use a CL or C stub to call your RPG procedure. Unfortunately, >SQL will always call the trigger from the default activation group, which >is usually a bad thing if you specify *CALLER on the trigger. Also, to update By SQL do you mean embedded SQL? I've not seen any problems with commit transaction boundaries, and I've always user *CALLER on the trigger program whenever possible, specifically so that the trigger would execute within the default transaction scope. Am I missing something here? Pete Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall/
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.