
CHANGE USER
ServerLoginName is the login name used on the serv er for the user accessing the DBEnvironment. You are prompted for the serv er login name only if you enter the client login name.
The MPE/iX serv er login name follo ws MPE/iX naming con ventions for a user name and is not
Only one server login name is allo wed for each client node name and client login name combination. When possible, the serv er login name and the clien t login name should be the same. This a voids problems in some applications that mak e assumptions about clien t and server logins. Refer to \Clien t and Server Login Names" under
In this example, one user prole is c hanged. The clien t login name of glen is replaced with charly . The server login name is also c hanged.
netutil=> change user
Client Node Name/Session Type Name (current value): cnode.cdomain.corg Client Node Name/Session Type Name (new value) (opt):
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, m ultiple proles are c hanged. The clien t node name is changed from cnode.cdomain.corg to cnode1.cdomain1.corg1 . First the curren t value for the client node name is entered, then the new value is entered. Entering an asterisk (*) for the client login name, causes all proles in the NETUsers le ha ving 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.corg1 Client Login Name (current value): *
Profiles qualified: 2
Change all (y/n)? y
Profiles changed.