|
Charles:
Try a google search for "os/400 ile procedure cross-reference" (without
quotes).
HTH,
Mark S. Waterbury
On 2/8/2017 3:19 PM, Charles Wilt wrote:
I'm working with a code base that doesn't include a "namepace"
prefix/suffix on procedures.
There's also not a direct correlation between the source file containing
the PR and the *SRVPGM with the procedure.
Now I can use DSPPGM, see the SRVPGMs bound in and do a 5=Display on each
to eventually see the procedures in the SRVPGM: DSPSRVPGM
DETAIL(*PROCEXP)
Is their anyway to determine directly where a given procedure used in a
program is coming from?
Basically looking for a DSPPGM DETAIL(*PROCIMP)
I realize that the procedures are bound by ordinal number, as opposed to
name...so the name may not be stored explicitly in the *PGM object. But
seems like some behind the scenes resolving either by an IBM utility or a
user written one could happen.
Actually, what would be really nice is too be able to know where the
procedure was found at CRTPGM bind time when *LIBL was used to resolve the
service program. Basically like how DSPPGMREF shows where the file on an
f-spec was found at compile time. But I'm probably out of luck with that
unless there's something stored within the object as part of the debug
listing.
Thanks!
Charles
--
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
As an Amazon Associate we earn from qualifying purchases.
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.