Re: protecting ISPF dataset allocations
- From: HMerritt@xxxxxxxxxxxxx (Hal Merritt)
- Date: 18 Mar 2009 07:34:17 -0700
Some might argue that it is a programmer's job to screw up and break stuff.
Give them the READY prompt back.
Protect your resources and don't worry about how folks do things. Any restrictions just make their job harder than it needs to be.
Wait. Are you a competitor? If you are, then disregard and put as many restrictions on your programmers as you can think of. That makes your costs go up, stifles innovation, and our sales people much happier :-)
My $0.02 (before taxes)
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@xxxxxxxxxxx] On Behalf Of Jousma, David
Sent: Wednesday, March 18, 2009 9:00 AM
To: IBM-MAIN@xxxxxxxxxxx
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.
Dave
_________________________________________________________________
Dave Jousma
Assistant Vice President, Mainframe Services
david.jousma@xxxxxx
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 listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
NOTICE: This electronic mail message and any files transmitted with it are intended
exclusively for the individual or entity to which it is addressed. The message,
together with any attachment, may contain confidential and/or privileged information.
Any unauthorized review, use, printing, saving, copying, disclosure or distribution
is strictly prohibited. If you have received this message in error, please
immediately advise the sender by reply email and delete all copies.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.
- References:
- protecting ISPF dataset allocations
- From: Jousma, David
- protecting ISPF dataset allocations
- Prev by Date: Re: protecting ISPF dataset allocations
- Next by Date: Re: protecting ISPF dataset allocations
- Previous by thread: Re: protecting ISPF dataset allocations
- Next by thread: Re: protecting ISPF dataset allocations
- Index(es):
Relevant Pages
|