SYSPROGs are subject to the role concept just like any other employee or contingent worker. Whether their role is broad or narrow is a shop specific decision, thus influencing the application of granularity. The length of granularity is optional based on one's shop's philosophy.
-----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Ted MacNEIL Sent: Saturday, April 03, 2010 1:44 AM To: [email protected] Subject: Re: Heads Up: APAR IO11698 - New SAF FACILITY class definition required for any SMP/E use >Data set protection alone isn't granular enough. >It's all or nothing for update access and this change allows more granular control. Yes, you're right it is simple, but (personal attacks aside) why is this needed? Are we going to be changing the roles of SYSPROGs so that one does a RECEIVE, one does an APPLY, etc? That kind of granularity is required? - Too busy driving to stop for gas! ------------------------------------------------------- --------------- 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 ---------------------------------------------------------------------- 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
