Of course you would craft your profiles to suit your situation and preferences.
However, coding each one is a PITA to manage and grant access. Not to mention an opportunity for a keying error. Personally, I'd go for a resource GIM.** granted to sysprogs to make sure they have all the juice they could ever want/need. Then I'd code exception profiles for those functions needing the granularity. For example, I could add a profile GIM.CMD.RECEIVE and grant access to both sysprogs and the production batch ID. -----Original Message----- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Patrick Lyon Sent: Thursday, May 13, 2010 11:16 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Heads Up: APAR IO11698 - New SAF FACILITY class definition required for any SMP/E use ..snip I say 'potato', you say 'potatoe'. :) I see your point, but I'm still defining discrete profiles here, and we are a small shop. Only two sysprogs with one working manager. We have a few scheduled jobs that kick off that do SMP/E work, like REPORT and RECEIVE. I guess my fear is of someone getting SURROGAT to that ID and could wreak havoc, which of course, is unlikely, but possible. So that ID only gets those attributes. ..snip 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
