ODBC Server Installation and Management Manual

Using the NonStop ODBC Server Configuration
Manager
HP NonStop ODBC Server Installation and Management Manual—429395-002
3-38
Help Screens
Help Screens
You can open a help file by choosing it from the Help menu with the mouse pointer or
by using the keyboard equivalent ALT H H. The contents of the help file that pertain to
a selected topic are displayed on the monitor.
Configuration Sequence
To avoid receiving warning messages during the configuration process, you should use
the NonStop ODBC Server Configuration Manager screens in the proper sequence so
that no entity is configured before another entity upon which it depends for definition.
For example, you should create a user profile before you reference it when adding a
username.
The optimum screen sequence for configuration is illustrated in the sample
configuration session that follows.
A Sample Configuration Session
This sample configuration session with the NonStop ODBC Server Configuration
Manager, presented with step-by-step instructions, is provided with the intent to help
the database administrator or NonStop ODBC Server administrator configure the
system. It gives the administrator a sense of how to set up the new system catalog with
the SCS, server class, profile, and username definitions. This sample session also
illustrates the best sequence in which to configure the various NonStop ODBC Server
entities to minimize warning messages that can result from unresolved dependencies.
This example is based on the assumptions that the product (client and server) has
been installed according to the instructions in Section 2, “Installing the NonStop ODBC
Server,” and the system catalog has been installed.
The first SCS a database administrator configures, during the installation phase, has
only a default server class. The maximum number of servers is three. After this SCS
has been configured, you can use the NonStop ODBC Server Configuration Manager
to configure the new SCS and server classes.
Using the status command,
NOSCOM> status scs $dba
you can see that you have the SCS and one server running. You could also have
RUNFILTR running and observe the EMS messages.