"Jousma, David" <[email protected]> wrote in message
news:<a90766b5039c59409110c92d47216f5903332...@s1flokydce2k322.dm0001.in
fo53.com>...
> 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

Yes, there is: DYNAMIC ALLOCATION INTERFACE ROUTINE, IEFDB401.

CLI   S99VERB,S99VRBAL    DSN-ALLOCATION REQUEST?  
 ...
CLC   S99TUKEY,=Y(DUNDDNAM) DDNAME  UNALLOCATION?.  
 ...
Check ddname in S99TUPAR
 ...
Refuse dynalloc request if desired.

Kees.
**********************************************************************
For information, services and offers, please visit our web site:
http://www.klm.com. This e-mail and any attachment may contain
confidential and privileged material intended for the addressee
only. If you are not the addressee, you are notified that no part
of the e-mail or any attachment may be disclosed, copied or
distributed, and that any other action related to this e-mail or
attachment is strictly prohibited, and may be unlawful. If you have
received this e-mail by error, please notify the sender immediately
by return e-mail, and delete this message. 

Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries
and/or its employees shall not be liable for the incorrect or
incomplete transmission of this e-mail or any attachments, nor
responsible for any delay in receipt.
Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal
Dutch Airlines) is registered in Amstelveen, The Netherlands, with
registered number 33014286 
**********************************************************************

----------------------------------------------------------------------
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

Reply via email to