× 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, Buck:

That's why I heartily recommend Alan Campin's excellent advice to "prefix" all exported procedure names with the name of the containing module. This eliminates the possibility of those kinds of "namespace collisions."

HTH,
Mark S. Waterbury

> On 2/8/2017 4:32 PM, Buck Calabro wrote:
On 2/8/2017 3:58 PM, Mark S Waterbury wrote:
Try a google search for "os/400 ile procedure cross-reference" (without
quotes).
I use the QBNLSPGM API to build a table of service program / procedure
names that I Q&D query with ad hoc SQL. Not sure if that answers the
original problem though, because I have a similar problem. Imagine
these 2 service programs:

CUSTOMER
getName
getAddress
getEmail
getCreditRating

VENDOR
getName
getAddress
getEmail
getIndustryCode

Now I have a mainline program that has:
name = getName;

Which getName is this particular line of code bound to? I've been doing
DSPPGM and eyeballing which service programs are bound, but Charles'
question has spurred me into looking at it in more detail. I think that
the QBNLPGMI API will do the other half: from program to service program
(PGML0200).

With two tables; one cross referencing procedure to service program, and
the other cross referencing program to service program, I could more
easily query which service program(s) are used by a given program +
procedure combination.



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.