|
A PEX trace will get you the raw data, then use SQL to ferret out the calls.
Used to do that quite a bit back in the day, but I’ve lost the SQL since then
On Apr 13, 2026, at 11:29 AM, David Gibbs via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:--
On Apr 13, 2026, at 10:56 AM, gio.cot <gio.cot@xxxxxxxxxxx> wrote:
Do you mean a list of programs that a specific program calls, the current call stack, or something else?
I mean this : at the end of job, i would like for example to have a list of all the call executed in that job ..
Thanks
I’m not aware of any way to do that kind of thing … there are API’s to get the call stack.
You can use the DSPPGMREF command to see what programs are referenced.
There are also a number of utilities available that do static program call analysis … like hawkeye, abstract/probe, & x-analysis.
david
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2026 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.