As careful as I was setting up zOSMF I missed one Permit.
PERMIT BBG.ANGEL.IZUANG1 CLASS(SERVER) ID(IZUSVR) ACCESS(READ)

Thank you, John, for pointing me to the IZUSEC sample.

On Fri, Mar 30, 2018 at 11:18 AM, Mark Pace <pacemainl...@gmail.com> wrote:

> Okay - found the error -
> 2018-03-30T13:28:47.907Z|00002644|com.ibm.zoszmf.navigation.servlet.
> NavTreeServlet|NavTreeServlet::doPost()
> SEVERE:IZUG593E: A SAF request failed. Additional information:
> "null"
> com.ibm.zoszmf.util.auth.AuthorizationException: IZUG593E: A SAF request
> failed. Additional information: "null"
>    com.ibm.zoszmf.util.nav.auth.NavAuthorizationManager.
> getAuthorizedNavigationTasksOfUser(NavAuthorizationManager.java:813)
> <snip>
>
> SAF - Something new to research.  :)
>
> On Fri, Mar 30, 2018 at 10:59 AM, Mark Pace <pacemainl...@gmail.com>
> wrote:
>
>> Thank you, Ronald and John.
>> This system is not in a Plex, just a single z/OS.  Should I still move it
>> to /global?
>>
>> I'll let you know what I figure out.
>>
>> On Fri, Mar 30, 2018 at 10:52 AM, John Eells <ee...@us.ibm.com> wrote:
>>
>>> First, make sure that your IZUPRMxx member's JAVA_HOME points to the
>>> right Java path.  z/OSMF requires Java 8 in z/OS V2.3.
>>>
>>> There should be two STDOUT and two STDERR data sets among the IZUSVR1
>>> outputs. The second of each one is more likely by far to be useful than the
>>> first of each.
>>>
>>> Then check /var/zosmf/data/logs/IZUG0.log.  The log files are
>>> space-limited, so if IZUG0 got full the messages of interest might have
>>> evaporated from IZUG0.log; if so you will have look for them in
>>> IZUG0.log-IZUG9.log.  You will need to su to UID(0) to read the files. ISPF
>>> OPT3.17 is an easy way to read them using the VA (view ASCII) line command.
>>>
>>> If all else fails, of course, please open a PMR!  If you do, I'd be
>>> grateful if you sent me the PMR number.  I have a high degree of interest
>>> in z/OSMF setup issues, and I will be interested to know what the problem
>>> was.
>>>
>>> Finally, consider moving the z/OSMF data directory to /global from /var
>>> and doing the necessary update to the PROC (update USERDIR) before you
>>> actually do anything with z/OSMF.  This will make z/OSMF use the same data
>>> repository no matter what system in the plex it starts on first, or gets
>>> moved to.  This should work and play better with z/OSMF autostart and avoid
>>> some possible entanglements later on.
>>>
>>> --
>>> John Eells
>>> IBM Poughkeepsie
>>> ee...@us.ibm.com
>>>
>>>
>>> ----------------------------------------------------------------------
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
>>>
>>
>>
>>
>> --
>> The postings on this site are my own and don’t necessarily represent
>> Mainline’s positions or opinions
>>
>> Mark D Pace
>> Senior Systems Engineer
>> Mainline Information Systems
>>
>>
>>
>>
>
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
>
>
>


-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Reply via email to