|
David, We have been using I/O servers for several years. The number 1 biggest drawback to using RPGIII for these was the inability to make recursive calls. I would estimate that 50% of the time we spent developing these servers was spent preventing the possibility of a recursive call. When we re-wrote these servers in ILE we chose to use a single CL that calls an RPGIV sub-procedure that then calls a file specific RPGIV sub-procedure. The overhead of the extra two calls is fairly small and gets around the recursive call problem. Others may question the benefits of recursive calls in triggers or I/O servers, but in our environment I am certain we have saved hundreds of hours writing applications because of this capability. David Morris >>> "David Prowak" <prowakd@emi.com> 10/24 8:42 AM >>> Hi, I have a MASTR_FILE that has a trigger attached to it. It's a *BEFORE, *UPDATE trigger, allowing repeated changes. Under certain circumstances, when the master record is changed, I then need to make changes to 4 other records from the MASTR_FILE. So what happens is that when I go to change the 1st of the 4 records, the trigger program is called again, and I get an error because of the recursive call. How should I handle this situation? I really want to define the business rules for this application in the DB, but I'm stuck. I believe that recursion is supported in CL and RPG IV procedures, so could/should I write my trigger using those constructs? Or should I write some info on the 4 records that need to be changed to a DTAQ, and then process those in batch later? I hoping the list can help me out. Thanks, Dave +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-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 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.