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



<Doug>
I have a program with the BNDDIR keyword in the CTL-OPT line. That binding
directory has several service programs in it.

My program [PROGA] uses two [PROCA, PROCD] of the 5 procedures in one of
the service programs [SRVA] in the binding directory. It uses just 2 of
the 5 available.

Is there any way, whether CL command, DB2 IBM I Service, or API [or
anything else] that will tell me the individual references *PGM object
PROGA needs? Something like: PROGA references PROCA in service program
SRVA, and PROGA references PROCD in service program SRVA?

I'm looking for something similar to the "Statically bound procedures"
section of a compile printout.

Any ideas?
</Doug>

... life could be very easy, if one is following very easy guidelines:
- make your export names unique by qualifying (prefixing) the exportname by the name of the module
- don't use CRTBNDxxx, use CRTxxxMOD and CRTPGM and CRTSRVPGM instead
- use DSPMOD detail(*EXPORT) and detail(*IMPORT) to an outfile
- et voila: you have a repository for your cross reference purposes

This would solve all problems with duplicate exports in BNDDIRs too.
I like easy living and I don't use BNDDIRs, imnstead I name all needed Modules and SRVPGMs at CRTPGM/CRTSRVPGM.
I don't use UPDPGM and UPDSRVPGM.
And I prefere rebinding after changes and not to use BinderSource wherever possible.

Life could be so easy...

D*B

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.