Yes. The "other" alternative is to not protect OPERCMDS (i.e. let everything
be authorized), but that's really not a good option.
It's not a difficult process, and for the simplistic stuff you are doing to
modify a simple started task, it's just the MVS.MODIFY.STC.** one you have to
worry abou
W dniu 31.08.2020 o 07:10, Brian Westerman pisze:
Even if you maintain SDSF via SAF (which you have to do by z/OS 2.5 because
that's all that will be supported) you will still have to update the RACF
OPERCMDS class (TSO RACF option 2 (general resource profiles)).
The profile name you need to u
Thank you for your response
So I believe I need to introduce RACF OPERCMDS even if it is maintained by
ISFPRMXX.
On Mon, 31 Aug, 2020, 9:11 am Brian Westerman, <
brian_wester...@syzygyinc.com> wrote:
> Even if you maintain SDSF via SAF (which you have to do by z/OS 2.5
> because that's all tha
Even if you maintain SDSF via SAF (which you have to do by z/OS 2.5 because
that's all that will be supported) you will still have to update the RACF
OPERCMDS class (TSO RACF option 2 (general resource profiles)).
The profile name you need to update (for MVS batch and STC's) is MVS.MODIFY.**,
: Sunday, August 30, 2020 8:41 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: IEE345I Modify invalid authority
Hello
I am trying to issue a command using SDSF batch and I end up with
IEE345I Modify invalid authority failed by MVS
We have secured SDSF using ISFPRM
My ID and group are part of NTBL in
Hello
I am trying to issue a command using SDSF batch and I end up with
IEE345I Modify invalid authority failed by MVS
We have secured SDSF using ISFPRM
My ID and group are part of NTBL in ISFPRMxx and group name is assigned
under the GROUP which maps to my RACF Group (Default)
We are in zOS
