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


  • Subject: RE: Retrieve CRTBNDRPG source file name
  • From: Buck Calabro <mcalabro@xxxxxxxxxxxx>
  • Date: Fri, 12 Nov 1999 15:44:12 -0500

Bill,
Because you can bind modules from many different libraries, and each module
can come from different source files, there is no "one" source
file/lib/member to display.  You can use a DSPPGM to an outfile, rip through
that and process each module with a DSPMOD, put THAT into an outfile and
query the lot (assuming the modules are still on the system.)

Alternately, look into the QBNLPGMI API.  It is documented in the Program
and CL API reference.

Buck Calabro
Aptis; Albany, NY

> -----Original Message-----
> From: Bill Brosch 
> Sent: Friday, November 12, 1999 2:00 PM
> To:   'RPG400-L@midrange.com'
> Subject:      Retrieve CRTBNDRPG source file name
> 
> Hi
> 
> Does anyone know how to programmatically retrieve the source
> lib/file/mbr name that was used to create a bound RPGLE program
> (CRTBNDRPG)?
> 
> A DSPOBJD just returns blanks.
> 
> TIA,
> 
> Bill Brosch
> Swift Technologies 
> 
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.