On Mon, 4 Jul 2011 18:52:15 +0300, Binyamin Dissen <[email protected]> wrote:
>On Mon, 4 Jul 2011 11:40:05 -0400 Gerhard Postpischil <[email protected]> >wrote: > >:>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. > >It is possible via a SAF exit. Every module LOAD goes thru there and the exit >could save the information to be printed during ACTRT. Sorry, Binyamin, but it's not true that every module LOAD goes through SAF: (1) Loading of LPA-resident modules will not in general go through SAF, though in some cases it will if for the first module LOADed as part of a new task. (2) Loading of modules that reside in a UNIX file system don't go through SAF in the same way, and are not really identifiable to the SAF exits involved with UNIX, either. -- Walt Farrell IBM STSM, z/OS Security Design ---------------------------------------------------------------------- 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
