× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Hi, Ira:
**
Trying to understand your "requirements" ... could you provide a little more information?

1.

are you trying to do this in the debugger?

2.

is this OPM RPG/400 or ILE RPG IV or some other language?

3.

what language(s) are involved? OPM or ILE or a mixture of both?

4.

are you talking about CALLs (on the stack) to inner procedures, or
external *PGMs, or both?

5. or are you trying to access these parameters at runtime? (ie. not
in the "debugger" but "programatically"...)

Depending on what language is involved, the "scope" rules of the language will dictate what is "addressable" ... the "name space" is typically the local variables of the currently active procedure, plus any "global" variables for that program -- and that's usually it. There is normally no "up-level addressing" provided by languages like C or RPG IV or COBOL ...

If you can explain why you want to do this, or what you hope to achieve, perhaps we can suggest some alternatives?

Hope that helps,

Mark S. Waterbury

> On 4/30/2012 5:48 PM, Ira Frosch wrote:
Hello all - longtime lurker, but never posted.

I'm trying to retrieve the entries up the stack - which I can do without a problem - but now I want to see the parameters that were passed with that entry. For instance:

Prg 1 Param1 Param2
Prg2 Param2 Param3
Prg3 Param4 Param5

I'm in Prg3 and trying to get the parameter 2 of Prg1. Any thoughts?

Thanks,
Ira

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.