-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Jousma, David Sent: Wednesday, March 18, 2009 9:00 AM To: [email protected] Subject: protecting ISPF dataset allocations
All, Is there any mechanism or approach to protect a TSO/ISPF user from accidentally/intentionally FREEing SYSPROC or SYSEXEC? Until now, our shop has been mostly Roscoe users outside of tech support. We are trying to migrate developer's to use TSO/ISPF, and want to protect the environment where needed. I don't mind them using ALTLIB, and LIBDEF to create their own "stuff", but I don't want them FREEing and reallocating SYSPROC/SYSEXEC to concatenate their own stuff ahead of what we want them to use. We already do not allow them to get to the READY prompt, but testing shows that even when in ISPF I can still FREE SYSPROC/SYSEXEC. I want to allow some ingenuity, just not too much is all. =20 <SNIP> Once they screw this up and can't go anywhere, their only out is "LOGOFF". When they log back on, it will all be fixed up again. After doing this a few times, they will be tired of the pain and stop doing dumb things. OR, they will get real smart and learn how to do it the right way, which is the ingenuity you are trying to encourage, right? And by preventing getting to the "READY" prompt, are you getting in the way of using TSO TEST to be able to diagnose certain problems? After all, you did say these are programmers, and unless you are using some other debugger (such as my favorite, XDC), how do you expect them to interactively diagnose and fix problems? Just my .00002 cents worth (highly devalued due to inflation...) Regards, Steve Thompson -- Opinions expressed by this poster may not reflect those of poster's employer. -- ---------------------------------------------------------------------- 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
