While I strongly agree with Bob, I will add that IF you feel the need to go down this path, there is a Dynamic Allocation Exit (IEFDB401) that you could use to accomplish this. The exit will require a detailed understanding of dynamic allocation, as well as an understanding of the various environments that this can be used in (not limited to interactive TSO), so I would reccomend avoiding this path.
=============================================== Wayne Driscoll Omegamon DB2 L3 Support/Development wdrisco(AT)us.ibm.com =============================================== Bob Shannon <[email protected]> Sent by: IBM Mainframe Discussion List <[email protected]> 03/18/2009 09:09 AM Please respond to IBM Mainframe Discussion List <[email protected]> To [email protected] cc Subject Re: protecting ISPF dataset allocations In my opinion it's overkill. Years ago I sent inordinate time trying to protect things like this. Educate your users and encourage them to be productive. Show them the advantage of using ALTLIB. If they free SYSPROC/SYSEXEC and then can't function, close the problem as a user error. They'll catch on quickly. Bob Shannon Rocket Software ---------------------------------------------------------------------- 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 ---------------------------------------------------------------------- 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
