'user not authorized' message when accessing the View DEF USER screen
search cancel

'user not authorized' message when accessing the View DEF USER screen

book

Article ID: 385156

calendar_today

Updated On: 01-09-2025

Products

View

Issue/Introduction

When trying to execute the View DEF USER command to access the Userid Definition Panel, I receive a 'User not authorized' message.

View is configured with SARINIT parameter SECURITY=EXTERNAL.

 

Environment

z/OS, View, DEF, USER, COMMAND, DEF USER, userid, not, authorized, external, security, internal, authorization

Cause

Insufficient access

Resolution

A. Have someone who has MASTER authority (See SARINIT parm MASTER=????????) log on to View and access the DEF USER screen.

B. Have the MASTER user locate the Userid of the user having the problem, and give the problem user MASTER authority by changing the value showing in the 'M' column for that problem user to a 'Y' and pressing the enter key:  

 CA View ALL -------------- Userid Definition Panel ------
 Command ===>                                             
                      --- Last Access ---      AEESSJ     
Sel Userid   Password Date       Time     M L   O O   Mode
    probuid           12/30/2024 09:17:40 Y RW YNNNNN ALL


C. Then have the problem user logoff of View and then back on, and see if they can get to the DEF USER screen.

D. If they are still receiving an error, press the PF1 key and send support a screen print showing them specifically what error they are receiving on their screen.

E. Determine what protocol the problem user is using to sign on to View (i.e. Are they logging on through a TSO/ISPF clist? through CICS? through VTAM? etc...) so that when security debugging is turned on via SARINIT FEATURE=1,  you will know where to look for the security call and failure messages that will be issued if the user is denied access to the DEF USER screen again.

- If signon is through a CLIST, then look in the users TSO LOGON profile.

- If signon is through a protocol that involves the XMS task, then the security call & failure messages can be found in the XMS task logs.