On 7/4/2011 7:42 AM, Hilary Hurwitz wrote:
I really miss one function - provided by FAQS/ASO.
At the end of every batch job, it printed out a list of
modules used and which libraries they were taken from.
The short answer to this is that it's not possible. If you look
through the archives, the topic of identifying a module's source
has come up repeatedly, without satisfactory solution. The basic
problem is that zOS has more options for loading modules, even
of modules that don't exist before or after execution; a single
load request may be satisfied from a concatenation of (user)
libraries, or from system libraries, or from storage.
If you go to www.cbttape.org you will find thousands of
contributed programs. There are some that will analyze JCL
libraries, and provide module and library information (but
limited when symbolic parameters are used). This will give you a
list of modules on EXEC PGM= operands. But a module may be
loaded from a library other than one appearing on a JOBLIB or
STEPLIB DD, so that alone doesn't help.
If you look at SMF records, again they will provide PGM=
information, but not the library. And modules that are loaded
dynamically won't show up anywhere.
It is possible to modify zOS (dynamically and temporarily) so
that it intercepts all requests to load modules, and there may
be something on the CBT for that. I also think that there may be
commercial packages that include this capability, but I've never
used one.
One inexpensive, but not foolproof way, would be to get a
directory listing for your load libraries, and see if any of the
member names appear in load module text (messy and error prone).
Gerhard Postpischil
Bradford, VT
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
