RE: Anybody know a good way for a program to see what's on its job's call-stack? -- MIDRANGE-L

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

Subject: RE: Anybody know a good way for a program to see what's on its job's call-stack?
From: Justin Taylor <JUSTIN@xxxxxxxxxxxxx>
Date: Mon, 30 Apr 2018 13:47:54 +0000
List-archive: <https://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <https://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <https://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

I use the Retrieve Call Stack (QWVRCSTK) API from RPG to get calling program info. That sounds like what you're looking to do.

-----Original Message-----
From: James H. H. Lampert [mailto:jamesl@xxxxxxxxxxxxxxxxx]
Sent: Friday, April 27, 2018 3:34 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: Anybody know a good way for a program to see what's on its job's call-stack?

Anybody know a good way for a program to see what's on its job's call-stack? Preferably something that can be called from ILE RPG.

I'm in a situation where, in order to catch a bug that has started breeding duplicate records in a file (apparently in some periodic update process), I need to be able to write something that will, when the suspect program is called, log what called it -- the entire call stack.

--
JHHL

As an Amazon Associate we earn from qualifying purchases.

This mailing list archive is Copyright 1997-2025 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.