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



There's not any useful system-provided tool for this. I wrote myself a
tool -- it extracts the exported symbols from each module and displays them
in a UIM list. Just a quick & dirty, but it works. There's an API that
extracts this information from modules.

Stu



On Thu, Feb 7, 2013 at 8:11 AM, Jeff Young <jyoung0950@xxxxxxxxx> wrote:

All,
I have an ILE program that consists of 1 main RPGLE module, 2 service
programs and 4 other modules used by this program.
The main program uses some procedures from the service programs and others
from the bound modules.
Given the following in the main module: GetMyValue (parmA : parmB : parmC)
How do I find what module the procedure GetMyValue is located in?
I *had* thought it would appear in the DSPPGM info, but I can not find it.

The issue I am having is that I am receiving an error from the GetMyValue
procedure, but the message does not identify what module is issuing it. I
can (and have) used DEBUG to step into this, but was looking for a better
way.

Thanks,

--
Jeff Young
Sr. Programmer Analyst
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.