×

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.




"it apparently doesn't capture the source file info for ILE program objects"

It can't.

Consider, an ILE program object could contain multiple *MODULE objects bound by copy, (not the ideal build strategy - but it could). These *MODULES could be a mix of languages, (e.g. COBOL, RPG IV, CL, C) - so there is no sensible way of saying that xxxxx *PGM is derived from yyyyy source code.

The *MODULE object(s) contain the source file information, not the *PGM.

Use DSPPGM to determine the *MODULEs, then DSPMOD to determine the source file/member. Unfortunately neither command provides an *OUTFILE capability, so you may wish to resort to retrieve or list APIs: QBNLPGMI, QBNLMODI, QBNLSPGM, etc.) - or the equivalent (SQL-based) IBM i Services, (e.g BOUND_MODULE_INFO view).

This is an area where commercial tools such as X-Analysis, Pathfinder, Abstract, Observer, etc. really excel.

Brian.

On 24/06/2026 19:26, Richard Schoen wrote:
Hi All,

When using object statistics against object in an IBM i library, it apparently doesn't capture the source file info for ILE program objects.

Does anyone know a way to retrieve the source info for an ILE program object ?

I also tried DSPOBJD and the same source file info is missing.

I guess the main question is how to determine which source was used to build an ILE object ?

I wonder if DSPPGMREF would do that.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>



This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2026 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.