That's what I was thinking. Hiding parmlib puts a rock in the road, but
you can just walk around it.
A long time ago I remember trying to compress parmlib in place and found
a started task had it allocated in its JCL. I can't remember why that
was - I assume to read bits and pieces at various times. So maybe
there's a legitimate reason for at least that one task to read parmlib.
On 2/3/2022 11:56 PM, Bruce Hewson wrote:
Hi Peter,
1. Seems auditors want security by hiding stuff
2. Access to PARMLIB means that someone can see what datasets can be APF
Authorized.
3. Access to PARMLIB means that someone can see what SVC could be loaded.
not sure why else.
and there are other ways to find the above information if I already logged in
to TSO or OMVS to be able to read the PARMLIB datasets.
Regards
Bruce
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
