RE: Function Opinion

[Dave Boettcher <DBoettch@xxxxxxxxxxxxxxxx>]

I thought the definition of a service program was something like what I read
in an article on Midrange Programmer by Kevin Vandever : "A service program
is a collection of subprocedures that perform a set of services. "  What is
the purpose of having one procedure in a service program?  Why not just use
a copybook and /COPY statements?
It seems to me that your maintenance of binding directories (one per
program) would out-weigh the convenience of only using one procedure per
service program.

JMHO, 

Dave Boettcher

-----Original Message-----
From: Johnson, Duane [mailto:djohnson@xxxxxxxxxxxxx]
Sent: Wednesday, October 15, 2003 10:28 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Function Opinion


  Oh, Thank you very much.
  I prefer to use one module per service program.  Maintenance is greatly
simplified, I can use a binding directory (one per program) to define all
the modules and service programs used, and I NEVER have to worry about
binder language, signatures, etc.

Duane

-----Original Message-----
From: Bob cozzi [mailto:cozzi@xxxxxxxxx] 
Sent: Wednesday, October 15, 2003 9:37 AM
To: 'RPG programming on the AS400 / iSeries'
Subject: RE: Function Opinion

That has to be the dumbest thing I have ever heard of with regards to
Service Program design.
Bob Cozzi
Cozzi Consulting
www.rpgiv.com