HPlogo ALLBASE/NET User's Guide: HP 3000 MPE/iX Computer Systems > Chapter 4 NETUtil Reference

ADD USER

» 

Technical documentation

Complete book in PDF
» Feedback

 » Table of Contents

 » Glossary

 » Index

Use the ADD USER command to add a user profile to the NETUsers file on the server. The first time you use this command to add a user profile, the NETUsers file is created. To display the contents of one or more user profiles, use the SHOW USER command.

ADD USER can be abbreviated to AU.

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.

NETUtil Syntax

   netutil=> ADD USER

   Client Node Name/Session Type Name: ClientNodeName

   Client Login Name: ClientLoginName

   Server Login Name: ServerLoginName

Parameters

ClientNodeName

is the node name of the client system.

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 the login name of the user on the client.

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.

Any or all of the client user login name components may be wildcarded using the "@". When this is done, only the non-wildcarded components need to match the user's actual login. For example, a client login entry of @.acct7,group6 would allow any user in the acct7 account and group6 group to have access to the server login name.

If more than one client login name entry matches the actual user's login, then the highest prioritized match will be used in determining the server login name. Prioritization is as follows: A fully qualified entry has highest priority (user7.acct3,group2). A fully wildcarded entry has the lowest priority (@.@,@). When dealing with individual components, an actual match for a specific component takes priority over a wildcard match. When a conflict with this arises between different components, then the account is prioritized first, the user second, and finally the group. For example, @.acct3,@ would have a higher priority than user2.@,group1, so the corresponding server login for @.acct3,@ would be used.

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 login can be wildcarded with the use of the "@" symbol.

The client login name is stored and displayed exactly as it was entered.

ServerLoginName

is the login name used on the server for the user accessing the DBEnvironment on the server. This name follows MPE/iX naming conventions for a login 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. (For guidelines on specifying session and group names in the server login name, see "Assigning a Server Login Name" under "Setting Up ALLBASE/NET on the Server" in the "Setting Up ALLBASE/NET" chapter.)

The server login name allows the client node name and the client login name to be mapped to a single login on the server. Only one server login name is allowed for each client node name and client login name combination. When possible, the server login name should be the same as the client login name. 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 "Setting Up ALLBASE/NET" chapter.

Example

   netutil=> add user

   Client Node Name/Session Type Name: cnode.cdomain.corg

   Client Login Name:glen.orders,purchasing

   Server Login Name:glen.orders,purchasing



   Profile added.



   netutil=>
Feedback to webmaster