|
You're right - you cannot modify the trigger buffer. That is why I suggested your trigger program check the number of parameters. That way if you do a direct call to the trigger program, and pass it no parameters, then it can translate what your saying into a 'go to sleep' command. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com Mark Adkins <adkinsm@xxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 09/30/2004 05:19 PM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To rpg400-l@xxxxxxxxxxxx cc Fax to Subject Re: RPG400-L Digest, Vol 3, Issue 742 Triggers are called by the database, so I can't modify any of the trigger buffer. The library lists are set up correctly, so everything can be updated by Excel. The trigger fires at the delete not the commit or rollback, so if I don't modify the trigger at all to handle commitment control, then everything it does can not be rolled back. I'm just having some trouble getting around some performance related open data paths in a trigger and having no way to close them without yanking the activation group. Regards, Mark > ----- Message from rob@xxxxxxxxx on Thu, 30 Sep 2004 14:22:29 -0500 ----- > To: RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> > Subject: RE: Commitment control and open data paths with triggers > > Well, in theory you could write your trigger program to check the number > of parameters. Then you could just manually call your trigger program > from the CL or whatever and not pass it any parms. Then, the trigger > could say, "Hey I didn't get any parms. I'm going to bed.". RCLACTGRP > can get expensive. But if you're always coding your trigger programs to > that activation group that's one method to do a kill them all with one > command shot. Curious, what happens if your trigger is fired off by > someone doing an update to the file via Excel, or command line access > doing UPDDTA? then again, a trigger with a bad library list might be one > way to stop users from trying to update those files. The update won't > work because the trigger should fail. > > Rob Berendt > -- > Group Dekko Services, LLC > Dept 01.073 > PO Box 2000 > Dock 108 > 6928N 400E > Kendallville, IN 46755 > http://www.dekko.com -- 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.