× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




----- Original Message -----
From: "Bill Graziano" <Bill.Graziano@besi.com>


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

I use a single library approach with the following naming conventions for
the source files:

QxxRPG    - RPG III Source
QxxMOD  - ILE Modules
QxxEXE    - "MAKE" source for compiling ILE programs.
QxxDBF    - Database source. DDS or SQL
QxxDSP    - Display file source.
QxxPRT    - Printer file source

The "xx" denotes a particular module within the software package. For
example; AP, AR, GL etc. The main reason that I prefer a single library
approach is because it's less of an effort to navigate the source using a
tool like PDM.

Regards,

John Taylor
Canada

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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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.