Re: Regarding source physical file

On 7/3/2023 1:48 PM, Patrik Schindler wrote:

Hello Buck,

Hallo Patrik!

Am 03.07.2023 um 18:02 schrieb Buck Calabro <kc2hiz@xxxxxxxxx>:

Is it possible to have all the source code placed in a single file for all the source members which are present there in different libraries in to corresponding source physical files?

Yes, for a programmer this is possible.
But why would one?

Because then sources are in one place. Fits my workflow much better than things being scattered around more or less arbitrarily by type.

For Joe's benefit:
The traditional source arrangement is aligned with the compiler defaults like
LIB1/QCLSRC
--hundreds of members
--each member having variable number of LOC
LIB1/QDDSSRC
--hundreds of members
--each member having variable number of LOC
LIB1/QRPGLESRC
--hundreds of members
--each member having variable number of LOC
...etc



I'm familiar with organising source like
LIB1/QSRC
--hundreds of members
--each member having variable number of LOC
LIB2/QSRC
--hundreds of members
--each member having variable number of LOC
LIBn/QSRC
--hundreds of members
--each member having variable number of LOC



I understood that Joe wanted:
QGPL/QSRC
--one member
--that one member having millions of LOC - all of the source lines from every member, source file, and library on the system in one, SQL-able place, ie select * from qgpl.qsrc;

...but perhaps I was mistaken. It is this last arrangement that I could not understand. I think it is doable with a pair of tables; one a 'master' table holding source PF attributes and a surrogate key, and the other being the source keyed by that key. As I think about it some more, now I wonder if he's thinking of keeping the many default QxyzSRC files in all of the libraries, but building a separate index that points to them all? It depends on whether he wants to search over the 50 character member text, or the actual lines of source.