ODBC Server Installation and Management Manual

Installing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
2-24
Installation Steps
catalogs. If you change SQL/MP table ownership, you should run NOSCOM SYSCAT
REFRESH before proceeding.
See Section 4, Managing the NonStop ODBC Server, for a discussion of ownership
and security.
Step 9—Configure the SQL Communication Subsystem
(SCS)
SCS configuration is driven from data stored in NonStop ODBC Server system catalog
tables. These tables contain descriptions to configure the SCS process, the network
protocol and service, the NonStop ODBC Server processes, and the server classes
and the associations among them.
You start an SCS process by using the following utility statement:
NOSCOM> START SCS scs-name
The process of installing the NonStop ODBC Server optionally loads a minimal
configuration necessary to start an SCS, connect through the Configuration Manager,
and proceed with manipulating the configuration attributes of the target system.
A configuration can be verified by using the utility statement INFO CONFIG. The
following example shows the configuration as it is established during the installation
process:
NOSCOM> info config $nsoad
INTERVAL CHECK (SECS): 60
NOS OBJECT FILE: \N1.$ODBC.ZNOSR2.NOS
NOSUTIL OBJECT FILE: \N1.$ODBC.ZNOSR2.NOSUTIL
NOSUTIL PRIORITY: -1
NOSUTIL CPU: -1
INPUT BUFFER SIZE (BYTES): 2448
OUTPUT BUFFER SIZE (BYTES): 2448
EMIT EVENTS: Y
PIPE TEST: N
MEMORY CHECK: N
SYSTEM CATALOG: \N1.$D1.ODBC2SYS
SCS LAST UPDATED: 29Apr96 8:22
SERVERS CONFIGURED: 3
NETNAME: ODBC2000
--------
PROTOCOL: TCP/IP
IOP: \TESS.$ZTC0
SO_KEEPALIVE: 1
SO_REUSEADDR: 1
NET LAST UPDATED: 25Apr96 9:11
SERVER NAME: NSOADMIN
------------
CPU LIST: -1
USE AS DEFAULT: Y