ODBC Server Installation and Management Manual

Managing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
4-2
Configuring SCS Server Classes
The preceding display shows two major classes of statistics: statistics on connections
and connection attempts (“Connected” column) and statistics on listening servers.
These statistics provide useful information on processes and their activities.
To begin configuring a server class, analyze customer applications and usage, possibly
determining that any given workstation runs multiple ODBC/DBLIB applications.
Additionally, each application probably is used by different groups of users. It is
impractical to address all applications and user groups as a whole.
Instead, break down the problem. First, segregate the applications. Then, within each
application, segregate users into groups. Each group represents a Guardian user ID
under which servers in a server class will run.
Now examine the problem relative to each application or user group. Each application
or user group will become a NonStop ODBC Server class.
Additionally, when using “off-the-shelf” applications, you should assume that an active
user can consume two connections to SCS and, therefore, two NonStop ODBC
Servers. This rule is based on experience attempting to connect some “off-the-shelf”
tools to the NonStop ODBC Server.
Example
Your analysis reveals that an application or user group will have 100 members. Of
these, only 30 are expected to be connected and doing work at any given time. Also,
you are not familiar with the off-the-shelf application software. In this case, it is good to
suppose that each active station will require two connections to SCS and thus two
servers. Finally, you expect two or three stations to attempt to connect simultaneously
at any given time.
For each application/user group, do the following:
•
Set AVAILABLE_SERVERS slightly higher than the expected number of
simultaneous connection attempts. For this example, set it to 10 to be
administrator. This allocation provides an available pool of 10 servers for those
attempting to connect, allowing up to five stations to connect simultaneously. Set
MAXSERVERS to 75, the worst-case scenario if everyone in the application/user
group is connected and working.
Connected Total The total number of client connections received by $ZYX. This
number is incremented for each client connection received.
Connected High The highest number of simultaneous client connections
serviced by $ZYX.
Connected Current The number of clients currently connected to $ZYX.
Listening Current The total number of available servers in each class.
Listening Hit The number of times a client connection request could be
satisfied from the pool of available servers.