Re: Database access as service pgm or bind by copy?

Jade,

Last February/March there was quite a discussion on the openerp400 list
about using a service program (per file) to manage all gets/updates.

It started with managing record lock conflicts, moved to the use of
service programs and digressed to security issues.

The question was raised about program maintenance.  The idea behind a
service program is that so long as the signature does not change you
avoid recompiling all the application programs as you would with a bind
by copy.

This seems to work OK as long as you are just adding new fields to the
end of the file, but if you change the length of a field in the middle
you gain nothing in the maintenance effort department.

Most of the same people involved in that discussion also subscribe to
this list and I would really like to hear if they have new insight upon
the past 9 months of actually doing it.  Especially if they will share
with us -how- they solved certain issues.

Jade Richtsmeier wrote:

>  We're trying to decide what is the best route to go with our database
> 'server' programs.  Do we create them as a service program or do we
> bind them by copy to each program that uses them. We've read many
> places that service programs should be used for common utilities and
> routines that many programs or applications use.  Bind by copy should
> be reserved for modules that perform lower-level routines within a
> larger program but are not shared among many programs or
> applications.  Okay, that said, what category does a database 'server'
> program fall into.  My guess is that the answer will be.......'it
> depends'.

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---