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



I'll wager you have performed a Bind By Copy on two *MODULEs, (CH0005 and CH0010) to create a *PGM object whose name also happens to be CH0005. The naming may have caused a little bit of confusion.

By default, DSPPGMREF OBJTYPE(*PGM) will show you objects at *PGM level - irrespective of which *MODULE they might be used in. (Just for giggles, place CH0010 in a *SRVPGM and perform a Bind By Reference - the files won't be listed at all.)

You might obtain a clearer picture by,

DSPPGM PGM(CH0005) DETAIL(*MODULE) - find out what *MODULE objects are bound to this program

DSPPGMREF PGM(CH0005) OBJTYPE(*module) - determine what files are used in each *MODULE
DSPPGMREF PGM(CH0010) OBJTYPE(*module)

Hope this helps.

Brian.

PS. Is CH0010 used by anything other than CH0005? If so, *SRVPGMs are your friend!

On 02/09/2017 21:09, tim wrote:
i have an rpg program ch0005 that uses a module.

D ch0010          PR                  ExtProc('CH0010')
d   paycode                      2    const

the module uses the following files:

Fshbahdt   uf a e           k disk
Fthmestl1  if   e           k disk
frlicqa22  if   e           k disk prefix('CL_')


When i do a dsppgmref, the files are listed, but as used under Ch0005, not ch0010.

Is there a way to see what modules use what files?



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.