It has been a while since I supported OPS/MVS, but where I was, there was a
security environment built with OPS Rules. It was based upon the userid of
the requestor and was set to allow or disallow functions with OPS/MVS.
I think the rules dataset we used ended in 'security.rules'.
We would update the appropriate member(s) and then deactivate and
reactivate them. Make sure you reset them to auto-enable.
You may have to enable them via console commands as you may not have all
the authority to work within the SPF application.
Bill Bishop
On Wed, Feb 22, 2023 at 10:16 AM Steve Beaver wrote:
> I'm in a shop that the person that setup OPS/MVS is gone.
>
>
>
> So I went looking and found that the SYSTEM is using FACILITY.
>
>
>
> What am I missing? It's has to be something minor and stupid
>
>
>
> From: Beaver, Steve
> Sent: Wednesday, February 22, 2023 10:07 AM
> Subject: OPS/MVS
>
>
>
> Current OPSVIEW command not authorized - ATTEMPTED OPSMVS SYSVIEW PANEL
> ACCESS BY A819822 REJECTED,
>
>
>
> Also since I am the SYSPROG and have SPECIAL. I have added myself to with
> READ
>
>
>
> FACILITY OPSAOF
>
> FACILITY OPSBRW
>
> FACILITY OPSCMD
>
> FACILITY OPSCTL
>
> FACILITY OPSDOM
>
> FACILITY OPSEPI
>
> FACILITY OPSGLOBAL
>
> FACILITY OPSHFI
>
> FACILITY OPSLOG
>
> FACILITY OPSOSF
>
> FACILITY OPSPARM
>
> FACILITY OPSREPLY
>
> FACILITY OPSREQ
>
> FACILITY OPSRMT
>
> FACILITY OPSSMTBL
>
> FACILITY OPSSSMTBL
>
> FACILITY OPSWTO
>
>
>
> What am I missing, and I also the logoff/Logon
>
>
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN