ODBC Server Installation and Management Manual

Installing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
2-26
Installation Steps
•
If you are using NonStop ODBC Release 1, the simplest check is to use
TDBSRV:STATUS at the TACL prompt. This command lists all of the processes
started by the SCS server. The syntax for this command is:
TDBSRV:STATUS SCS-config-file
where SCS-config-file is the name of the SCS configuration file used to bring
up the system.
Here is sample output from the STATUS command:
NOSCOM> status scs $nsoad
SCS_NAME: \N1.$NSOAD
JOB_ID: 1
PROGRAM_FILE: \N1.$D1.ODBCSYS.SCSOBJ
SWAPVOL: \N1.$SWAP.#0116894
HOMETERM: \N1.$OSP
PRIORITY: 140
USERID: 255,255
PARENT USERID: 255,255
PROCESS TIME: 271808
•
If you are using NonStop ODBC Release 2, use the NOSCOM STATUS
command.The syntax is:
NOSCOM STATUS SCS-name
•
You can use the various SCF commands described in Section 4, Managing the
NonStop ODBC Server, to check on the status of SCS and the associated NonStop
ODBC servers.
•
If you started RUNFILTR, check the messages it prints to ensure that SCS has
started. This is a sample of RUNFILTR output when an SCS process is started and
it prestarts one NonStop ODBC server (to improve readability, the output records
have been reformatted slightly from what you see on the screen):
94-11-17 08:59:21 \TESS.$ZT1 Tandem.SCS.D42
000007 $ZDSS.1: process $ZT1 object state changed to started
94-11-17 08:59:22 \TESS.$ZT1 Tandem.SCS.D42
000007 $ZDSS.1: session @Listener object state changed to starting
94-11-17 08:59:24 \TESS.$ZT1 Tandem.SCS.D42
-32750 \TESS.$ZT1: Process started (T9245D30 26OCT94)
94-11-17 08:59:46 \TESS.$ZT1 Tandem.SCS.D42
000007 $ZDSS.1: server \TESS.$X716 object state changed to defined
94-11-17 08:59:46 \TESS.$ZT1 Tandem.SCS.D42
000007 $ZDSS.1: server \TESS.$X716 object state changed to starting
This example shows five trace records. The SCS process is named $ZDS1 (set by
process-name in the SCS section of the SCSCFG* configuration file). The first
three records detail the starting of the SCS process and the last two the starting of
an NonStop ODBC server process named $X716.
•
Run NOSCOM and execute the utility statement STATUS SCS scs-name.