Re: Regarding source physical file

Am 04.07.2023 um 23:20 schrieb Jon Paris <jon.paris@xxxxxxxxxxxxxx>:
Attachments don't work on the list Daniel.


Jon P

On Jul 4, 2023, at 4:16 PM, Daniel Gross <daniel@xxxxxxxx> wrote:

Full Ack for "bad idea", but in fact, with today's SQL you can really make
it very dynamic.
Just take a look at this GIST from Birgitta:

[1]gist-og-image.png
[2]List all Source Code Lines - for Scan
gist.github.com

Could easily be wrapped in a view or in a UDTF.
Daniel

Am 04.07.2023 um 19:34 schrieb Jon Paris <jon.paris@xxxxxxxxxxxxxx>:

Agreed Daniel, except that you would have to automate the recreation of
the View/UDTF to account for new/deleted source members.
It is really just a bad idea.
Jon P.

On Jul 4, 2023, at 12:37 PM, Daniel Gross <daniel@xxxxxxxx> wrote:

Of course - WHY? Is a good question.

But I would create

a) a table function (UDTF)

or

b) a view

which consolidates all members in one “query”.

In this case there would be no “not-up-to-date” problem.

But I also see no real advantage of this - better place your source
into IFS and use GIT and GREP and CAT and whatever you like.

HTH

Daniel

Am 04.07.2023 um 18:26 schrieb Jon Paris <jon.paris@xxxxxxxxxxxxxx>:

Haven't you had enough answers to this question already?

Of course you _CAN_ do it. It is a pretty simple programming task to
create such a file. But what then? How do you update that file
when the source code of a program changes?

In all of your posts on this topic I have yet to see you explain WHY
you want to do this and what benefit you think you will get. If you
want it for the purposes of impact analysis then how do you plan on
handling the potential impact of overrides? How do you deal with
program calls when the calls are via a variable target?

Not to mention that placing every source file from every library
together is probably not terribly useful as it will mush together
programs from multiple applications. Far more useful to separate
them by application surely?

And on and on.

Question For You Joe. Notice that among the many who have responded
to your question not a single person has told you that they already
do this, or that it is a good idea should give you a hint that
perhaps you are exploring a dead-end path. Why not tell us WHY you
think you need this and let the hundreds of highly experienced
programmers who frequent this list offer you suggestions on
practical ways to achieve your objectives?

Jon P.

On Jul 3, 2023, at 3:41 AM, joe <joe.planet21@xxxxxxxxx> wrote:

Hi,

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?

And the output of that file should be like something if we do
sql/runqry

over it then should be able to see it's members separately i mean
when one

member ends and another starts clearly with proper source code

readability like we read it separately individually to that member
when we

do wrkmbrpdm and do option 5 to browse it from it's source (from
it's

corresponding library and source physical file)

Any help in this regard would be highly appreciated.

Thanks

--

This is the RPG programming on IBM i (RPG400-L) mailing list

To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/rpg400-l

or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx

Before posting, please take a moment to review the archives

at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

--

This is the RPG programming on IBM i (RPG400-L) mailing list

To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/rpg400-l

or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx

Before posting, please take a moment to review the archives

at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

--

This is the RPG programming on IBM i (RPG400-L) mailing list

To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/rpg400-l

or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx

Before posting, please take a moment to review the archives

at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription
related questions.

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.
Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.

References

Visible links
1. https://gist.github.com/BirgittaHauser/282b4f3f590da4b2774610b1b6ca7e58
2. https://gist.github.com/BirgittaHauser/282b4f3f590da4b2774610b1b6ca7e58
--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.

--
This is the RPG programming on IBM i (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related questions.