× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



> >>Is it possible to have a trigger program update the record whose update
>>triggered it without having it re-trigger itself infinitly?
>
>To enable it, specify ALWREPCHG(*YES) [Allow Repeating Change]
>on the ADDPFTRG command, which also must be a *BEFORE trigger.
>Any changes you make to the buffer will then be written to the file.  
>Note that the original caller's program buffer is *not* modified, so if it
needs
>to see the changes made it needs to reread the record. 

I second this.  I have triggers that change the record that fired the
trigger and they are working with ALWREPCHG(*YES).  I will add that you
should NOT write the code like the example in the DB programming manual.
The example actually hardcodes the from/to positions of the record.  MUCH
better would be any of the versions that have been posted here of late.
Some "gotcha's" would include specifics about your environment: journalling,
commitment control and NULL values.  Send me private email if you'd like a
copy of the version I am using (none of the above specifics.)

Buck Calabro
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.