Aha! I just reread the question. Sorry, ignore the below; I didn't read carefully the first time.
--- Bob Bridges, robhbrid...@gmail.com, cell 336 382-7313 /* Beware of any Christian leader who does not walk with a limp. -Bob Mumford */ -----Original Message----- From: Bob Bridges <robhbrid...@gmail.com> Sent: Saturday, November 7, 2020 21:12 Disclaimer: I used to know RACF a lot better than I do now. The following may be wrong. As I recall the RACF documentation, it DOES NOT CONSULT the access rules for a dataset if my ID is the same as the HLQ. This should mean, despite what others say here about UACC and the ACL, that ordinary access rules will have no effect on your ability to access your own datasets (where "own" means your ID is the same as the dataset's HLQ). I expect an exit could modify this. Someone else mentioned global variables; I don't know about that. Now everyone feel free to jump on me. But that's what I recall reading, long ago (but not THAT long ago). You didn't specify RACF in your question. In Top Secret it's definitely possible to withhold permission to execute your own datasets...or rather, it's possible to give ownership of those datasets to someone else, even though your ID matches the HLQ. Ownership is not defined by default. ACF2...it's been too long. ACF2 used to be my first security system, but I haven't used it in about ten years now. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Frank Swarbrick Sent: Friday, November 6, 2020 16:43 In the Unix world one can use chmod (change mode) on their own files to make it so non-superusers cannot view a particular file. Is there anything similar for MVS data sets? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
