<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>
We have approached this by enforcing a standard set of concats at logon. *EVERYONE* runs this concat at logon. After that they are on their own. BTW This also extends to panel libraries. <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. </SNIP> We have a clist (in our case called RESTART) that can be run from the ready prompt to reinstate the standard concat w/o logoff. EX 'SYS1.CLIST(RESTART)' ---------------------------------------------------------------------- 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
