Re: Library and Source File Question

We also use a 3-library system: one for data files, one for programs, one
for source, and it seems to work pretty well. For example, one BIG
advantage of separating programs from data is that we can make a copy of
our entire data library and use it as a test area (what a luxury!) while
still using the programs in the production program library (we compile
new/changed programs into a separate "test object" library, but this way
we only have to compile what we changed, and not everything needed to run
the application).

As for source, we have one library with separate source members for each
system (ORDSRC for order processing, PURSRC for purchasing, etc.).
Personally, I like having all related source members together -- it makes
it much easier to move around from RPG to CL to DSPF (of course, if I were
using Code/400 I guess I wouldn't care so much about this. . . . :-)

midrange-l@midrange.com writes:
>I am in the process of setting up some standards for creating libraries,
>source files, objects, etc.  I have two questions that I would appreciate
>some help with.


Mike Naughton
Senior Programmer/Analyst
Judd Wire, Inc.
124 Turnpike Road
Turners Falls, MA  01376
413-863-4357 x444
mnaughton@juddwire.com