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



Right, and besides, this isn't a UNIX machine were you've got to code
everything yourself, its OS/400 where everything should just be there. :)


Bob Cozzi
Cozzi Consulting
www.rpgiv.com


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, September 16, 2003 2:36 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Procedure List

Perhaps Bob can expound on why.  But in "seeking first to understand" 
perhaps he wanted a list of all subprocedures to either:
a)  see if there are some out there that does what he wants to do, and 
let's put them in a service program.
b)  Put a subprocedure in a common service program that may already be in 
use by a program that has an internal subprocedure and he wants to make 
sure it doesn't conflict.  You know, pick a safe name.

Rob Berendt
-- 
"They that can give up essential liberty to obtain a little temporary 
safety deserve neither liberty nor safety." 
Benjamin Franklin 





Scott Klement <klemscot@xxxxxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
09/16/2003 02:26 PM
Please respond to RPG programming on the AS400 / iSeries
 
        To:     RPG programming on the AS400 / iSeries 
<rpg400-l@xxxxxxxxxxxx>
        cc: 
        Fax to: 
        Subject:        Re: Procedure List



> I have no problem getting at and retrieving the list of procedure names 
in a
> service program, but I can't get the list of procedure names used in a
> program object. The API (as well as the DSPPGM command) does not list 
the
> procedures used in program objects.

I don't understand why you want to do this. DSPPGM/DSPSRVPGM/APIs only
list the exported procedures from a program, that's true.  But, there's no
chance for a procedure name to conflict unless it's exported!   So, why do
you need to know about the ones that aren't exported?

>
> Is there an API or a CL command that I may have missed that does an
> "Enumerate Procedure Names" for program objects?
>

I doubt it.   Remember, those names are just to make life easier for
humans... a procedure is normally just an address in memory.   I don't
really see why the program object would still contain the names after a
compile?  Unless they're exported, of course, in which case other programs
have a need to get their addresses after the program has already been
compiled.

The only other idea I can think of is the debugger APIs.  Perhaps they
have a way to get the procedure names that are used during debug sessions,
or maybe the names used for error messages...
_______________________________________________
This is the RPG programming on the AS400 / 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.


_______________________________________________
This is the RPG programming on the AS400 / 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.