Rusty,

We have our objects in one library and data in another.  It is easier to
restore files from a tape when the data is in a separate library. The only
concern would be the number of libraries you have in your library list.
Most software companies put their objects and data in separate libraries. If
you use one library you have to be careful with your naming of your objects.

Our Source files are in separate source files too.  This makes it easier to
view the members for dspf, rpg, cl, etc. using PDM and not having to use the
position to and use the subset function.  You minimize the risk of someone
deleting a source member that they shouldn't have.
If you use one source you have to be careful with your naming convention.

What you could do is create a library and create one source file in there
and then copy all of your source file members into this new source file and
library and then have your people look at it to see if they like it or not.
If you already have then in one source file, then do the reverse of what I
am suggesting and see what everyone thinks.  You could do the same with the
objects and files, but this would take some time to do, because of the
access paths needing to be built over the PF in the new library.......and it
would depend on your DASD available.

Jim




-----Original Message-----
From: Rusty Luse [mailto:rluse@cronus.cc]
Sent: Thursday, October 03, 2002 9:15 AM
To: midrange-l@midrange.com
Subject: Library and Source File Question



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.




As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.