DOUBT REGARDING CHANGE OF NETMASTER FACILITY AND UAMS
search cancel

DOUBT REGARDING CHANGE OF NETMASTER FACILITY AND UAMS

book

Article ID: 190143

calendar_today

Updated On:

Products

NetMaster Network Automation NetMaster Network Management for SNA NetMaster Network Management for TCP/IP NetMaster File Transfer Management SOLVE

Issue/Introduction

Our pre-sales colleague--who is working with cust on several NetMaster deployments--sent us the following problem for us to open a case:
-

Per our conversation it follows details pursued by cust for the activity of: Update of a userID already existing in NetMaster:

SEC=NMSAF

The userID initially was created as $MDMON--or: PERMIT to NETMASTR.MON facility. It needs to be promoted to
$MDADMIN--or: PERMIT to NETMASTR.ADMIN.

Upon update of his permission in RACF (NETMASTR.ADMIN) the userID defined in UAMS remains with
GROUPID $RMMON.

What is the correct procedure to change it also in UAMS?

-

Environment

Release : 12.2

Component : CA NetMaster Network Management for TCP/IP

Cause

-

Resolution

The response was sent to our colleague--as follows:
-
   
There is a new SXCTL parameter applicable for this request (see highlighted text for value to be used):                                              
   
REMODEL NO | YES                                                       
   
Specifies whether a user's SAF model is checked at every logon.              
   
NO        (Default) Specifies that the model  is not checked.
   
YES      Specifies that the model is checked at every logon. If  the model has changed then the user's UAMS record is updated.
   
-  
   
Note: The following NetMaster techdocs page was updated to include the REMODEL parm info:
   

Additional Information

SXCTL Parameter File