ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

User gets BASEC003 trying to access /a function in Netmaster or SOLVE

book

Article ID: 112111

calendar_today

Updated On:

Products

CMDB for z/OS NetSpy Network Performance NetMaster Network Automation SOLVE NetMaster Network Management for SNA NetMaster Network Management for TCP/IP NetMaster File Transfer Management SOLVE:Operations Automation SOLVE:Access Session Management SOLVE:FTS SOLVE:Central Service Desk

Issue/Introduction

In a NetMaster or SOLVE region, a user or group of users is seeing this message
BASEC003 USER xxxxxxx NOT AUTHORIZED TO yyyy

This can manifest in different ways:
- a user (or group of users) has access to a function on one region but not another while UAMS and external security are the same.
- a user (or group of users) is missing access to a function after an upgrade with no changes to security.
- other scenarios may be possible.
 

Cause

NPF security  is different or missing

Environment

All SOLVE and Netmaster products

Resolution

1. Check page 5 of the UAMS definition for affected users to see if any of these fields are populated
    NPF Resource List Member .....                                         
    NPF Command Member ...........                                               
    NPF Message Member ...........
         
 
2.  If so, ensure that any listed members are contained in your TESTEXEC.

3. If upgrading or building a region on a new system,, check your old TESTEXEC for any members starting with $RMS* and ensure they are copied to your new TESTEXEC

4. Check the NPTABLES DD statement in your RUNSYSIN and compare with the prior release or working region.
    The default definition contains
     DD=NPTABLES,BLKSIZE=32720,DISP=SHR,DSN=hlq.TESTEXEC
         DD=*,DISP=SHR,DSN=hlq.CC2DEXEC 

     Perhaps you have additional libraries containing custom $RMS* members that need to be added.

If your problem still persists please contact CA Customer Support.