Re: RE: Single vs. Multiple Source Files (was Size of source physical files)

We use a hybrid system, which seems to work pretty well. We store all
source types in the same file, but we have multiple source files, named
after the applications. ACCSOURCE for accounting programs, MFGSOURCE for
manufacturing programs, etc. The member prefixes match the file prefixes,
so all the accounting source members begin with ACC and all the
manufacturing with MFG. This way, we don't have a huge number of members
in any particular file.

Thus, we always (well, almost always ;-) know where to look for the
source, and related things are grouped together (so if you want to change
both a screen and its maintenance program they are right next to each
other).

Also, we create all new source PFs with a record length of 112, and we
haven't run into any problems at all. .  .

RPG400-L@midrange.com writes:
>Another reason is that restore of members (if one should need it) takes a
>*long* time
>when thousands of members are placed in the same source file.


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

+---
| 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
+---