HP 3000 Manuals HP 3000 Manuals
CHANGE USER
Use the CHANGE USER command to change a user profile in the NETUsers file
on the server.
CHANGE USER can be abbreviated to CU.
[REV BEG]
To issue this command, you must log on as MANAGER.SYS, have SM
capability, or have AM capability for the account specified in the
command.[REV END]
NETUtil Syntax
netutil=> CHANGE USER
Client Node Name(current value): ClientNodeName
Client Node Name (new value) (opt): ClientNodeName
Client Login Name (current value): ClientLoginName
Client Login Name (new value) (opt): ClientLoginName
Server Login Name (current value): ServerLoginName
Server Login Name (new value) (opt): ServerLoginName
Change Profile (y/n)? {y[es]}
{n[o] }
Parameters
ClientNodeName is the client node name of the user profile you want
to change.
It follows the node naming conventions of the
datacomm services used by the client node. The
client node name is not case-sensitive and is stored
and displayed exactly as it was entered.
ClientLoginName is either the login name of the user on the client or
an asterisk (*).
The MPE/iX client login name follows MPE/iX
naming conventions for a login name and is not
case-sensitive. The session name is not allowed and
the group name is required. (For guidelines on
specifying session and group names in the server
login name, refer to "Setting Up ALLBASE/NET on the
Server" in the "Setting Up ALLBASE/NET" chapter.
The HP-UX client login name follows HP-UX naming
conventions for a login name, cannot exceed eight
characters in length, and is case-sensitive.
Refer to the ADD USER command for details on
wildcarding the client login name.
The client login name is stored and displayed exactly
as it was entered.
If you enter an asterisk, all client node names in
the NETUsers file that match the current client node
name are changed to the new client node name.
ServerLoginName is the login name used on the server for the user
accessing the DBEnvironment. You are prompted for
the server login name only if you enter the client
login name.
The MPE/iX server login name follows MPE/iX
naming conventions for a user name and is not
case-sensitive, The session and group names are
optional. The server login name is stored and
displayed exactly as it was entered.
Only one server login name is allowed for each client
node name and client login name combination. When
possible, the server login name and the client login
name should be the same. This avoids problems in
some applications that make assumptions about client
and server logins. Refer to "Client and Server Login
Names" under "Cross-System Connectivity" in the
"Getting Started" chapter.
Examples
In this example, one user profile is changed. The client login name of
glen is replaced with charly. The server login name is also changed.
netutil=> change user
Client Node Name/Session Type Name (current value): cnode.cdomain.corg
Client Node Name/Session Type Name (new value) (opt): Return
Client Login Name (current value): glen.orders,purchasing
Client Login Name (new value) (opt):charly.finance,stmts
Server Login Name (current value): glen.orders,purchasing
Server Login Name (new value) (opt): charly.finance,stmts
Change Profile (y/n)? y
Profile changed.
netutil=>
In this example, multiple profiles are changed. The client node name is
changed from cnode.cdomain.corg to cnode1.cdomain1.corg1. First the
current value for the client node name is entered, then the new value is
entered. Entering an asterisk (*) for the client login name, causes
all profiles in the NETUsers file having a client node name of
cnode.cdomain.corg to be changed to cnode1.cdomain1.corg1.
netutil=> change user
Client Node Name/Session Type Name (current value): cnode.cdomain.corg
Client Node Name/Session Type Name (new value) (opt):cnode1.cdomain1.corg
1
Client Login Name (current value): *
Profiles qualified: 2
Change all (y/n)? y
Profiles changed.