Tom Marchant wrote:
On Thu, 24 May 2018 13:30:20 -0500, John McKown wrote:
On Thu, May 24, 2018 at 12:40 PM Seymour J Metz <sme...@gmu.edu> wrote:
Have you looked at the MOD entries for the missing csects?
Yes, they look correct to me. The entries for each MOD (missing & not
missing) points to AOSBN as where it resides.
That's fine, but what LMODS are listed as containing those MODs?
It's the MOD entries that have subentries for the LMODs in which they
are included. So, let's assume for the moment that none of the members
of AOSBN are packaged as ++PROGRAMs, which would not be relevant in this
context. You have to LIST the MODs for all the members of AOSBN to see
which target library load modules and program objects are made up using
one or more of the MODs from that DLIB data set. Note that those load
modules and program objects thus identified might also include MODs that
represent members from other DLIB data sets.
Probably more to the point, if you want to know which MODs are
associated with a particular LMOD, then LIST LMOD(name) XREF will tell
you. Each of those MODs can point to a different DLIB data set; it's
not unusual for a load module to include MODs from several different
DLIB data sets.
--
John Eells
IBM Poughkeepsie
ee...@us.ibm.com
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
