× 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 Mark,

I already prefix my procedures with the name of the module at home and in the office like this:

*
* Opens a job log.
D JobLog_open...
D PR like(JobLog_handle_t)
D extproc('JOBLOG1_+
D JobLog_open+
D ')
D i_qJob const likeds(qJob_t)
D options(*nopass: *omit)
D i_options const like(JobLog_options_t)
D options(*nopass: *omit)
D i_direction const like(JobLog_direction_t)
D options(*nopass: *omit)
D i_strMsgKey const like(JobLog_msgKey_t)
D options(*nopass: *omit)

But now I even consider to add a domain name as it is common sense with Java packages:

*
* Opens a job log.
D JobLog_open...
D PR like(JobLog_handle_t)
D extproc('de.tools400.JOBLOG1_+
D JobLog_open+
D ')
D i_qJob const likeds(qJob_t)
D options(*nopass: *omit)
D i_options const like(JobLog_options_t)
D options(*nopass: *omit)
D i_direction const like(JobLog_direction_t)
D options(*nopass: *omit)
D i_strMsgKey const like(JobLog_msgKey_t)
D options(*nopass: *omit)


Thomas.



-----Ursprüngliche Nachricht-----
Von: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] Im Auftrag von Mark S Waterbury
Gesendet: Mittwoch, 8. Februar 2017 22:45
An: rpg400-l@xxxxxxxxxxxx
Betreff: Re: Is there something like DSPPGM that would should what service program procedures where bound into a program?

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.


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

Please contact support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate link: http://amzn.to/2dEadiD
--
IMPORTANT NOTICE:
This email is confidential, may be legally privileged, and is for the intended recipient only. Access, disclosure, copying, distribution, or reliance on any of it by anyone else is prohibited and may be a criminal offence. Please delete if obtained in error and email confirmation to the sender.


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.