ODBC Server Installation and Management Manual

Installing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
2-25
Installation Steps
SHUTDOWN SERVER: N
PRIORITY: 140
PROFILE: NSOADMINPROF
G_USER: SUPER.ODBC
AVAILABLE_SERVERS: 2
MAX_SERVERS: 5
IDLE DELETE DELAY (SECS): 60
NOS RUN OPTIONS:
INITIAL HEAP SIZE (KBYTES): 750
MAX HEAP SIZE (KBYTES): 750
SERVER LAST UPDATED: 25Apr96 13:11
TIMEOUT SECONDS: 0
This INFO CONFIG statement is the same statement used by the SCS when NOSUTIL
must return its configuration by name.
Step 10—Start the SQL Communication Subsystem
The procedure for starting the SCS is as follows:
1. Set the DEFINE for the location of the NonStop ODBC Server system catalog. Use
the ADD DEFINE command at the TACL prompt prior to starting NOSCOM.
2. If you need start-up messages, start the RUNFILTR macro supplied with the
NonStop ODBC Server. It prints system console messages generated by SCS and
is useful both for verifying that SCS has started and for troubleshooting (see
Troubleshooting on page 2-58 for further details).
3. You must run RUNFILTR from NOS-Target-Disk and on a separate terminal or
in a separate window. From a separate TACL prompt, type:
RUN RUNFILTR
4. Log on as a super-group user with sufficient authority to start a licensed process
under a different Guardian user name. To ensure having authority greater than or
equal to any user who may connect, you should log on as the super ID.
5. The SQL Communication Subsystem runs under this Guardian user name.
NonStop ODBC server processes associated with this SCS process are started
under this name, but then assume the identity of the Guardian user name indicated
for the server class definition.
6. To start SCS, issue the following command from a TACL prompt:
RUN NOSCOM START SCS scs-name
where scs-name is the identifier for an SCS configuration.
Verification
You can verify a successful SCS start in various ways.