If the problem you are trying to solve is important to the organization, ask
the people who can run DAF for what you need and let them sanitize the
output for you.

Alternately, if the number of libraries containing the modules in question
is not too large and you can convince the security admins to help, you could
create dataset profiles for the libraries in WARNING mode with access NONE.
Every load would then generate a message in the system log.  It wouldn't
tell you which module was loaded but it would tell you which library was
being accessed by which job step.

For a brute force method, if you have a test system you can use, recreate
the libraries without the members.  As each LOAD fails, add that member.
When the jobs finally run successfully, any members not added are likely

> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Farley, Peter x23353
> Sent: Wednesday, August 09, 2017 8:02 AM
> Subject: Re: Any SMF statistics available for LOAD of a program?
> Unfortunately I have no access to any SMF data here and I am prohibited
from running
> DCOLLECT for myself by security rules, so DAF while no doubt useful to
others is not
> much use to me here.
> These are old dynamically LOADed and called COBOL subroutines that we are
not sure of
> the actual usage.  If they ever do get LOADed and called they will DISPLAY
> information in SYSOUT, but that then requires reading the SYSOUT archive
extensively to
> determine whether they were ever actually used.  That also only answers
the question of
> usage for as far back as the SYSOUT archive holds, which can be an issue
if actual usage is
> (for instance) yearly or less often.
> Archive scanning is tedious but doable.  My initial request was part of
deciding whether we
> need to use the tedious path or not.

For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to