Did you try the ADDSD command? That will only work if: (1) your system uses RACF and (2) the dataset(s) in question start with your RACF id. This should work unless your system is secured in a truly extreme way.
ADDSD 'myracfid.*.**' UACC(NONE) Replace 'myracfid' with your RACF (TSO) id and this will make it so that almost nobody can read any of your datasets. If either of the above is not true, then you are out of luck unless you can get your security administrator to do the securing for you. Have you considered a 2x4 on people who mess around with your stuff without permission? <kidding!> I do understand the problem! I used to have people copy my JCL and programs. And then come to me screaming when it didn't do what they wanted. So, being the main sysprog __and__ security admin, I made it impossible for them to read my datasets at all. I also made it impossible for them to look at my job output in SDSF. My motto is: "Don't irritate the sysprog. You won't like the results." <twisted, evil grin> -- Q: What do theoretical physicists drink beer from? A: Ein Stein. Maranatha! John McKown ---------------------------------------------------------------------- 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
