On Tue, Sep 12, 2017 at 5:49 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

I do not do anything like this. I use a single source file, in my case,
QSRCF so for each service program I have

xxNAME - Top Level Binding instruction
xxNAME_B - Bindery
xxNAME_M01 to Mxx Modules.
xxNAME_PR - Prototypes

I have everything in one file. I would like to shoot the guy at IBM who
came up with QRPGSRC, QCLSRC, etc, etc. What a waste of time.

Going a tad OT, but I'm like you in that I just keep a single QSRC file in
my development libraries. I have no control over the production libraries,
but at least I can keep all of the source in one file while I'm
developing. Of course, with RDi's filters, it's no problem to "merge"
source members from multiple files into one list.

The problem I have with your convention using the _zzz extensions taking up
4 characters in the member names, is that you are now limited to naming
with 6 characters. I suppose if you're content with using meaningless
member names like AR123R, PY321C, etc., this is fine. But I feel limited
with the 10 characters we are given now. Hmmm, perhaps an RFE to increase
files' member names from 10 characters to, say, 30? When pigs fly, I'm

- Dan

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-2021 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.