In
<[EMAIL PROTECTED]>,
on 02/13/2007
at 12:58 PM, "Ward, Mike S" <[EMAIL PROTECTED]> said:
>Hello all, I have a small problem and I hoping to get some opinions
>on how to handle it. We had some datasets that were renamed, some of
>these were loadlib and some proclibs. These were development libs so
>there isn't much restriction on the libs themselves, but since some
>were proclibs, Jes2 had some jcl issues.
It's dangerous to allow your users to have write access to libraries
needed by the system, including JES2. You should RACF protect those
libraries and provide a change-control mechanism for updates. Uses can
test their procs with instream procs or with the use of JCLLIB.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
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
