Re: Regarding source physical file

Hi,

Thanks for all of these suggestions here.

Just to clarify exact specifications here:-

Main idea here is to have all the source code of all the members which are
there in a specific IBM i environment( with respect to their source code
present in source physical files and their respective libraries) in a
single file which could be queried up on to see the source code of any
intended source member uniquely and exactly the same way we see it once
manually we browse that specific source code once we do WRKMBRPDM (by
mentioning source member, source physical file and it's source library
name) and take option 5 against that source member to browse it's source
code there.


It would be very good if that file has real time data to have updated
source code present in it for all the source members in it.


Thanks



On Tue, 4 Jul 2023 at 04:22, Scott Klement <midrange-l@xxxxxxxxxxxxxxxx>
wrote:

IMHO, this is a bad idea.

But if you absolutely must do it, I would create a UDTF that combines
all of the members for a single query (possibly using RPG native I/O
with MBR(*ALL)) instead of copying all of the data to another file and
having to keep that file up to date. the UDTF could also add a new
"virtual" field for the member name.

But, I don't understand why he wants to reinvent the wheel... why not
use one of the existing time-tested tools for this?


On 7/3/23 4:36 PM, Sam_L wrote:

I'd guess what Joe wants is a file that has fields:

Library name, file name, member name, SRCSEQ, SRCDAT, SRCDTA
Keyed on Library name, file name, member name.

Then loaded from every source file on the system.

You can then scan this all you like with SQL.

Of course, you'll have to maintain it somehow as the contributing
source changes.

You could load the file by hand, one member at a time. Or you'd need a
program or a stored procedure to build the file all members at once.
Maybe someone will volunteer to do it, or contract with Joe to do it.
If The exact specification can be produced, if course.

(Joe sounds like tim ken...)


On 7/3/2023 2:28 PM, joe wrote:

for more clarification:-

In this ideal file I expect all the source members names distinguishly
mentioned (with respect to their source code present in corresponding
source physical files and libraries. ) along with their source code
across
entire IBM I system.

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