Re: Library and Source File Question

In my opinion (for what its worth - and thats not saying much)
1. a.Keep the data separate.
         If you have to create a test(development) and/or a QA (user 
acceptance) region, the data is separate from the programs, therefore the 
library list can reference the correct data library (PRODUCTION, QA, TEST) and 
still reference the program library.
    b. Security. Please consider this. The data needs to be updated (?) by the 
users, but the programs definitely do NOT. Keeping the data separate will make 
life easier as far as security is concerned.
2. The vendor supplies their program  executables separate from their sources, 
with each type of source separate in their own physical file. Anything 
developed in house, the executable and source reside in the same library, but 
the type within their own physical file. I cant say their is an advantage or 
disadvantage either way.
Anyway
Good luck, good hunting


>>> "Rusty Luse" <rluse@cronus.cc> 10/03/02 10:14AM >>>

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.

1.  Is there a major pitfall that I may encounter if I choose to setup a
library that will contain all objects for a particular application?
     This library would include all program objects and data files.  Should
I separate my data files into another "data" library?  Half of my
     coworkers think we should separate the data and objects while half
think it is easier to keep everything in one library.  What are the
     advantages and disadvantages?

2.  This question is similar to the first question except it deals with
source files.  Many of my coworkers believe that we should keep all
     of our source in one source file instead of separating them by QDDSSRC,
QCLSRC, QRPGLESRC, etc.  I prefer to separate my
     source but am not against changing if one source file is better.  Any
suggestions?


Thanks,
Rusty

_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.