|
I don't write my triggers assuming the update is coming from the 5250 session. I simply throw an exception message. Then I let the UI program use the %status, psds, etc to determine what to do. I think, even if you were going to go the external i/o route, assuming that your i/o routines are only called by a 5250 program would be a tad shortsighted. Hear you on the recursion. Don't often have a need for that particular example though. Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com "Fisher, Don" <Dfisher@xxxxxxxxxxxxxxxxx> Sent by: rpg400-l-bounces@xxxxxxxxxxxx 02/02/2005 11:53 AM Please respond to RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx> To "'RPG programming on the AS400 / iSeries'" <rpg400-l@xxxxxxxxxxxx> cc Subject RE: Externalizing I/O was RPG read loops Both. We're a small shop with only six developers. I admit to being the one pushing this architecture, though. As I understand it, another benefit is these access programs could eventually be tweaked to support browser based applications and "green screen" applications simultaneously. Tough to do that with triggers. Another problem with triggers is recursion. If I need to update a related record in the same file, I'd need to have my trigger program in a *NEW activation group, which creates a lot of overhead. Using access procedures in service programs eliminates that problem. As for stopping errant developers, a trigger could be used for that, though we don't here. Just my current opinion, which, of course, may change later. Donald R. Fisher, III Project Manager Roomstore Furniture Company (804) 784-7600 extension 2124 DFisher@xxxxxxxxxxxxx <clip> I get my enforcement of business rules with triggers and constraints. Stops even the errant developer who updates a file directly with any utilities. Again, only one place to maintain the logic. Don, are you the developer of these functions, or only a user? <clip> -- 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.