Re: Regarding source physical file

As mentioned earlier main intension to have all the source code placed in
a single file is for it to be available handy in terms of finding details
of a specific source member quickly by just running a simple SQL query over
it (that ideal file) and for avoiding identifying each source member's
source code at different places on each time.

There could be duplicate members with same name but it's fine as long as
they are in different places (in it's corresponding libraries and in it's
corresponding source physical files)






On Mon, Jul 3, 2023, 22:09 Jim Oberholtzer <midrangel@xxxxxxxxxxxxxxxxx>
wrote:

Better yet, just put all the source in the IFS. Now the extension to the
file name sets which compiler to use, you can have COMMAND, CLP, RPGLE,
DDS, etc all with the same name if you wish since the extension is part of
the name in the IFS. You can have folders/sub folders for version control
etc. Plus it works with GIT much easier. If you have any HTML or SQL in
the application it lives there too. RDi and VSCode work with the IFS very
well so why continue to use a file system that limits things? Back up and
recovery are just as easy.

I always journal the source files so mistakes can readily be reversed (you
would not believe how many times I get the “I deleted that by mistake, or I
forgot….”) and I can simply roll back the error. Also answers the “who
changed that source file member” question. IFS can be journaled too.

I use source file SOURCE. 99% of the time it works for everything, the
disadvantage is now a command and the command processing program must be
named differently, so compiling requires a bit of manipulation, same thing
with screens.

If you take a serious look at MERLIN and where IBM seems to be heading
with its future development, then you’ll have a hard thoughtful look at
using the IFS for source.

Jim Oberholtzer
Agile Technology Architects

On Jul 3, 2023, at 11:02 AM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 7/3/2023 11:16 AM, joe wrote:

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?

--
--buck

http://wiki.midrange.com
Your updates make it better!


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription

related questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.