The authorization checking in this case is not done by SDSF and
consequently issuing an ICH408I is not under its control. If you're a
RACF shop, list the resource profiles defined to the OPERCMDS class and
make sure the relevant profiles have the necessary users/groups in their
access list. For purging spool files, the resource profiles defined to
the JESSPOOL class may be relevant as well if you already have access to
the appropriate OPERCMDS resource.
For JES2, the relevant OPERCMDS profiles will likely be something like
JES%.CANCEL.*, JES%.SET.*, JES%.*. Refer to the "RACF Security
Administration" and the "MVS Planning: Operations" manuals for details of
the OPERCMDS and JESSPOOL classes.
Greg Shirey <[EMAIL PROTECTED]>
Sent by: IBM Mainframe Discussion List <IBM-MAIN@BAMA.UA.EDU>
08/10/2005 08:22 AM
Please respond to IBM Mainframe Discussion List
To: IBM-MAIN@BAMA.UA.EDU
cc:
Subject: Re: [IBM-MAIN] Any way to get SDSF to cough up ICH408I?
Tom,
I seem to recall that the last time we set up a new LPAR, we were getting
similar messages until we issued $S to JES2. Don't know if that's
applicable...
Greg Shirey
Ben E. Keith Company
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of Thomas Conley
Sent: Wednesday, August 10, 2005 8:59 AM
<snip>
I get NOT AUTHORIZED FOR CMD trying to purge my own output from the HOLD
queue. Another system programmer here gets NOT AUTHORIZED FOR CMD when
trying to add an initiator class from the INIT panel.
----------------------------------------------------------------------
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
