This is the good answer, some control plus flexibility. Dave Gibney Information Technology Services Washington State University
> -----Original Message----- > From: IBM Mainframe Discussion List [mailto:[email protected]] On > Behalf Of Staller, Allan > Sent: Wednesday, March 18, 2009 8:09 AM > To: [email protected] > Subject: Re: protecting ISPF dataset allocations > > Tom Conley's DYNAMIC ISPF may also provide a good approach. SEE > www.cbttape.org File 495. > > It doesn't directly address the free of SYSPROC/SYSEXEC, but it seems > to > offer an approach that limits the need to do this in the first place. > > <SNIP> > 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. > </SNIP> > > ---------------------------------------------------------------------- > 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
