|
As far as I know, it will always fire the trigger program. Commitment control has no effect on it. Did you put the trigger program in debug to make sure that it really did not call it? My guess is that the trigger program opens the file for output only, which cause the data to be held in the buffer. -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Mark Adkins Sent: Wednesday, September 29, 2004 3:01 PM To: rpg400-l@xxxxxxxxxxxx Subject: Commitment control and open data paths with triggers I have been reading documentation and setting up test scenarios all day and can't get past this last obstacle. I have a file called TEST with an RPGLE deletion trigger to write a history file TESTH. In the trigger, TESTH is left open for performance. I have a little test program that takes the commitment control flag as an entry parm. It deletes a record and then rolls back. When I call the program with commitment control on, it fires the trigger and rolls back just fine. In the same job, when I then call the program with commitment control off, it deletes the record but never fires the trigger. Keep in mind that I have to execute STRCMTCTL before running the program for the first time and can not ENDCMTCTL between the calls because TESTH is still open. This is a tough one. My everlasting gratitude to anyone who can help me get past this. Regards, Mark -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.