Re: Objects and Source

["alan shore" <SHOREA@xxxxxxxx>]

The original question was in reference to sources and the compiled executables. 
We keep the sources and executables in separate libraries. This way we can 
apply an authorization list to all the executables so that the different users 
have *USE authority on the executables, with *PUBLIC *EXCLUDE. The library 
containing the sources is only accessed by the programmer group with *USE 
authority (again *PUBLIC *EXCLUDE). This method allows  only the users within 
the programmer group the ability to copy the source to a TEST/DEVELOPMENT 
library to apply the necessary changes.

>>> Jim Langston <jlangston@conexfreight.com> 02/01 4:39 PM >>>
IMO, it is much better to keep the files and source libraries separate.
Although, in the file library I will put source for trigger programs, as
that makes more sense to me to be in the library where the physical
file is.

Also, what do you do when you have more than one library that uses
the same physical files?  There are some instances where it makes
sense to have separate libraries for separate programs, such as in
our case where we are running two separate companies on the same
computer, along with multiple sub divisions of one company.

One library is called Conex, the other is called MSL, in this scenario,
if you were to put the physical files with the source, which library would
you put them in?  And could you always find them?  And what happens
when someone who isn't thinking puts a copy of the physical file in the
other library?  Now you have a complete mess.

But, using a separate library for physical files (such as Files)  you know
where the physcial files are located.  And all the source code that goes
with the physical files (DDS source for physicals and logicals, and
RPG source for trigger programs).

I think that in a very small system, however, it might just be as easy to
have them all in one library.  But, of course, all companies grow (if they
want to make money they do) then you get into the situation where you
now have multiple libraries and get into the confusion state again.  I just
assume any system is going to get huge, and make it clean from the git
go.

Regards,

Jim Langston

Bill Graziano wrote:

> I know this isn't exactly an RPG question. However, the experts monitor this
> list.
>
> I am getting ready to add some long awaited structure to our AS/400. What
> are your recommendations regarding objects and source in the same libraries?
> I know some prefer to use separate libraries and some prefer to use the same
> libraries. Is this just a personnal preference or are there distinct
> advantages?
>
> Thanks in advance,
>
> Sincerely,
> Bill Graziano
> Programmer
> Brambles Equipment Services

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

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