RE: All the code in one place (was: OVERRIDES)

-snip excellent comments on keeping the working routines together-

>In the case of opening a file, part of
>the work is specifying which file
>to open.  If it's the RPG program's
>responsibility to open the file
>(which it pretty much has to be) then
>it's a GOOD idea to make sure that it's
>also the routine that does the override.

Agree! The hiccough is when there are ten files and (therefore) ten
overrides in an application that spans a dozen or so RPG programs.  Then I
need to specify essentially the same code a dozen times.  For a new
application, this may not be an issue, because I can put all the
open/close/get/put stuff into a single service program, but for a converted
classic application that's a bit impractical.

Your remarks on splitting the chores between the CL and RPG are right on the
mark.  It _is_ confusing and unnatural, but there's so much code that does
it, we're numb to the problem.

Nice thread!
  --buck