ODBC Server Installation and Management Manual

Installing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
2-53
Configuring Usernames and Attributes
to named server class configurations. Configuring items in other orders is allowed but
will produce warning messages to indicate missing referenced configuration utilities.
The following describes the basic steps for configuring the NonStop ODBC Server
attributes:
1. Create profiles representing different behaviors. If these profiles refer to tracing or
governing entities, those entities must also be set up.
2. Create the usernames and associate them with one of the profiles set up in Step 1.
3. Create any alias names needed and set up profiles for those alias names.
4. Register the user and alias names with one or more SCS entities.
You can repeat this sequence many times. You can build everything for one or two
usernames first—you are not required to create all the profiles and usernames before
creating an alias name, for example.
One requirement for the NonStop ODBC Server is that it can be installed and brought
up with a minimum of configuration. The NonStop ODBC Server achieves this by using
defaults for a number of items:
•
DEFAULT profile—the profile is named DEFAULT; NOSINST inserts a row for it in
ZNSPROF during the NonStop ODBC Server installation (the column values are all
set to default values).
•
Default server class—the user explicitly identifies one named server class
specification as the default server class for a specific SCS configuration. The same
server class can be used as the default in one SCS configuration and not the
default in another configuration.
•
Default Guardian user name—when a client connects with username xxx and no
username or alias name xxx is configured, the NonStop ODBC Server tries to
decode xxx to a Guardian user name as follows: if the username is of the form
ggg_uuu, the NonStop ODBC Server tries to use the Guardian user name
ggg.uuu (ggg represents a group name, and uuu represents a username within
that group).
In other words, if SQL.A and SQL.B are valid Guardian user names on the NonStop
system, then usernames SQL_A and SQL_B are configured by default. This feature
means that they can connect to and use the NonStop ODBC Server without having
been explicitly configured. The NonStop ODBC Server always assigns a DEFAULT
profile and the server class designated as the default to such users.
If you do not want the DEFAULT profile or default server class, you must configure a
username for SQL.A or SQL.B. You can use any logical name, including SQL_A or
SQL_B.
Utility statements such as ADD USER are used to add and delete usernames and their
attributes. These statements are described in the NonStop ODBC Server Reference
Manual.