is the login name of the user on the client.
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 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 client login name is stored and displayed exactly as it was
entered.
is the login name used on the server for the user accessing the
DBEnvironment on the server.
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 server login
name must reside in the /etc/passwd file.
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.