Re: Sql query to find whole call stack of programs

Hi Tim

The error you list is something you need to look into - the directory you are trying to upload to - can you see it on the system when you use the command WRKLNK on a command line on a 5250 terminal emulation? I assume you can log on to the system with mochasoft - and by the way, as far as I know, mochasoft has nothing to do with FTP - I've been wrong many times, so I'm happy to learn something new.

cheers
Vern

On 6/20/2023 1:42 AM, tim ken wrote:

Thanks , could you please share that program? Meanwhile I wanted to test
the attached program but can't test it currently on mochasoft as it does
not allow uploading text file in pub400.com due to error "550-Specified
directory does not exist or cannot be accessed.".

if it's possible for someone to test and share it's feedback regarding
achieving the desired result here?


https://code.midrange.com/c3a7d9466b.html


Thanks.


On Tue, 20 Jun 2023 at 02:56, Don Brown via RPG400-L <
rpg400-l@xxxxxxxxxxxxxxxxxx> wrote:

Frank Coleman wrote a utility to produce such a list by reading the source
code.

He does pop up on this list occasionally - you may see if he still has the
code, I think it will do what you want at a static source level.

If programs are chosen by dynamic library list changes as Buck suggests
then nothing will provide that list.

Cheers

Don





From: "Buck Calabro" <kc2hiz@xxxxxxxxx>
To: "RPG programming on IBM i" <rpg400-l@xxxxxxxxxxxxxxxxxx>
Date: 19/06/2023 08:39 PM
Subject: Re: Sql query to find whole call stack of programs
Sent by: "RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxxxxxxxx>

tim wrote:

i tried this 'SELECT * FROM
TABLE(QSYS2.STACK_INFO('123456/JOBNAME/JOBUSER')) based on the job( by
mentioning its corresponding job details) which ended in the system few
days back but this command ended in error with message id 'CPF503E'. "An
error occurred while invoking the associated program or service program
.........in library QSYS with error code 1- "the external program or
service program returned SQLSTATE 42704. The text message returned from
the
program is : job (my job details) NOT FOUND".

Right. That's because the call stack only exists during the time that
the programs are actually being executed. Once the job ends, there is
no call stack to look at.

The operating system itself does not know that PGMA calls PGMB, and
I'm not sure there's any way for it to know that. Imagine the
situation where you have PGMB in three separate libraries. Each
version of PGMB does something slightly different - perhaps it
calculates taxes based on region. The library list is changed
dynamically at runtime. How could the operating system know from a
compiled PGMA /which specific/ PGMB got called during job 123456?

I agree with Daniel that if there's no analysis tooling at your
workplace, you will either need to analyse the job by hand (starting
at the top CALL in the job log) or write your own tooling.
--buck
--
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 email has been scanned for computer viruses. Although MSD has taken
reasonable precautions to ensure no viruses are present in this email, MSD
cannot accept responsibility for any loss or damage arising from the use of
this email or attachments..
--
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.