Externalizing I/O, was Returning from a procedure

Is there anyone who likes this technique that didn't write the actual 
interfaces themselves?

Rob Berendt
-- 
Group Dekko Services, LLC
Dept 01.073
PO Box 2000
Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





Rick Rauterkus <ricker@xxxxxxxxxxxxx> 
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
05/24/2004 01:37 PM
Please respond to
RPG programming on the AS400 / iSeries <rpg400-l@xxxxxxxxxxxx>


To
"ALBartell@xxxxxxxxxxxxxx" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Re: Returning from a procedure






> For instance,  I just got done writing one service program that takes 
care
> of all our XML processing.  Behind the scenes the service program is
> accessing many files, but the interfaces I export are purely functional 
to
> the programmer.  One example would be EDI_processXMLReq(xmlFile); - that
> will receive in an XML file, parse it, log it, dispatch the appropriate
> business logic program to process it, and return an XML response. Within
> the EDI service program I access all of the files directly with CHAIN's
> READ's etc.  This gives me the same separation that I had in my CstMstPF
> service program except for it provides services or actions instead of 
just
> file access.

Just echoing Aaron's statement.  This is what we do also, this works
out very well.

AddCartonToSkid( Skid# : Carton# )
Carton# = NextSkidCarton( Skid# )
Serial# = CartonSerial#( Carton# )
DateShipped = CartonShipDate( Carton# )
etc.

Application program concentrates on what needs to be done, the service
program worries about how to do it and where the data is stored.  Also
makes it very easy to change your file layouts without affecting your
application programs.

Takes a little extra time, but well worth it.

Rick


_______________________________________________
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.