|
<ducking quickly> Of course you could always use the trigger to call the external program... ;-) -----Original message----- From: rob@xxxxxxxxx Date: Wed, 2 Feb 2005 16:38:04 +0000 To: RPG programming on the AS400 / iSeries rpg400-l@xxxxxxxxxxxx Subject: RE: Externalizing I/O was RPG read loops > 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? > > 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:18 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 > > > > > > > I used to think the same way. It took me quite a while to understand the > benefits of such functions. > > I've been experimenting with them here and have used them to make my file > updates, writes, deletes, etc. exist in only one place. The same logic to > perform these functions is executed each time one of these operations is > requested. It gives me the ability to enforce business rules and have > only > one place to maintain the logic. > > The case for procedures that merely return the data is more difficult, > except I've found these procedures integrate well with the update and > record > creation procedures. > > Donald R. Fisher, III > Project Manager > Roomstore Furniture Company > (804) 784-7600 extension 2124 > DFisher@xxxxxxxxxxxxx > > > <clip> > I think you're the first person that I heard of, that wasn't the person in > charge of writing the access programs, that actually liked this scenario. > Why an end developer would like to replace > > chain(e) myfile; > // now actually do some real work with the fields > > with > getFilename(); > MyWorkField1=GetField(field1); > MyWorkField2=GetField(field2); > ... > // now actually do some real work with the fields > > rather escapes me. > <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. > > > -- > 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. > Jonathan Mason www.astradyne-uk.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.