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. Dave _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Services [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB1G p 616.653.8429 f 616.653.8497 This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- 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
