Re: Call stack inquiry performance - QWVRCSTK vs QMHSNDPM+QMHRCVPM

If considering QMHSNDPM to find a program in the stack, it would be daft to try to find entries "one level at a time." Just send a diagnostic message to the named program, and if the error CPF24xx "program &x not in stack" is the result, then you know it is not in the stack.

However whenever a design exists where a program thinks it must know who called it, I start to wonder if I might not have a design problem. There should be very few required cases for that feature. It might be worth discussing for what purpose the program name is being passed and why the called program finds it necessary to validate the program name is on the stack.

Why the non-RPG topics finding their way here of late, instead of to Midrange-L?

Regards, Chuck

Lim Hock-Chai wrote:

I've a service program that accepts program-name as one of the input
parameters. When this parameter is passed in by the caller, it will
need to determine if the passed in Program Name is actually in the
current call stack. There are two ways that I know of that can
determine if a program is on the call stack, one is using the QWVRCSTK
api to get the current call stack; Another way is use the
QMHSNDPM+QMHRCVPM to get the call stack one level at a time. Does
anybody know which will perform better, or is there another way to
determine if a program is on the current call stack?