Re: DSPPGMREF and referenced libraries

*LIBL in the library name means that the calling program is not coded to find the called program in a specific library, rather it looks for the program but searching the library list. This is a standard IBM i technique and allows testing from test libraries

If you want to programmatically further search the called programs, you will need the production libraries in your library list.


On 6/30/2023 11:19 AM, tim ken wrote:

Thanks,

Does that mean (as per this command's manual in the link) "The referenced
object names and libraries listed may be different than the actual names of
the objects, since this information is stored when the program is created"

..That this command is generating wrong results i mean mix of right and
wrong for objects shown as referred and their libraries names.. it appears
so far to me.

And if that is the case then how can we get reference correctly for the
specific Program object which keeps calling multiple programs ?





Thanks a lot...

On Fri, 30 Jun 2023 at 20:10, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 6/30/2023 10:13 AM, tim ken wrote:

Not all the libraries it's showing incorrect but for many of them
unnecessarily it's showing incorrect and those names which it shows as
libraries names even don't exist in the system at all
also unnecessary putting '&' sign in the beginning of such names and

those

lib. names not at all exist in the system and even no object with that

name

exist.

Did you read the manual page for DSPPGMREF?
https://www.ibm.com/docs/en/i/7.4?topic=ssw_ibm_i_74/cl/dsppgmref.html
May I direct your attention to the Note just above the Restrictions.

I think that you will begin to understand a little more if you look at
the source for some of these objects - especially the CL programs having
a reference that starts with an ampersand (&).

did it happen as the moment i ran this DSPPGMREF for *all as mentioned
earlier then job went in MSGW and i had to ety it with 9999 and some

times

nomax ?

No. That message was telling you that the file was full.
Your response told the machine to allow it to grow larger.

--
--buck

http://wiki.midrange.com
Your updates make it better!


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.