Use the CHANGE USER command to change a user profile in the
NETUsers file on the server.
CHANGE USER can be abbreviated to CU.
You must have superuser capability to issue this command.
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.
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 HP-UX client login name follows HP-UX naming conventions for
a login name, cannot exceed eight characters in length, and is
case-sensitive.
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.
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.
This name follows HP-UX naming conventions for a login name,
cannot exceed eight characters in length, and is case-sensitive.
It is stored and displayed exactly as it was entered. The new
value must exist in the /etc/passwd file on the server or you
will receive an error message when the application attempts to
connect to the remote DBEnvironment. If the server login name
is different than the one in the /etc/passwd file, you need to
update the /etc/passwd file.
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 (current value): clientsystem
Client Node Name (new value) (opt): Return
Client Login Name (current value): glen
Client Login Name (new value) (opt): charly
Server Login Name (current value): glen
Server Login Name (new value) (opt): charly
Change Profile (y/n)? y
Profile changed.
netutil=>
|
In this example, multiple user profiles are changed. The client
node name is changed from clientsystem to othersystem.
The current value for client node name is entered, then the new
value is entered at the prompt. If an asterisk (*) is entered
for the client login name, all user profiles in the NETUsers
file that have a client node name of clientsystem are
changed to othersystem.
netutil=> change user
Client Node Name (current value): clientsystem
Client Node Name (new value) (opt): othersystem
Client Login Name (current value): *
Profiles qualified: 2
Change all (y/n)? y
Profiles changed.
|
