ODBC Server Installation and Management Manual

Installing the NonStop ODBC Server
HP NonStop ODBC Server Installation and Management Manual—429395-002
2-60
The SQL Communication Subsystem
You use the ADD TRACE utility statement to set up a trace definition, then use the
ADD PROFILE or MODIFY PROFILE statement to set the TRA_MODE_ON and
TRACE_NAME options.
To disable tracing for a given profile, just set TRA_MODE_ON to “N.”
The SQL Communication Subsystem
If the START SCS statement fails to bring up the SCS, check the following:
•
Check that your configuration is valid by using the INFO CONFIG statement.
•
Start RUNFILTR, then reissue the START SCS statement. Inspect the RUNFILTR
output for error indications. If other SCS processes are running, you can identify
records for your SCS by matching the process-name you set in the SCS section.
Two of the most common errors reported by the SCS during startup are:
See the NonStop ODBC Server Messages Manual for detailed information on these
and other event messages generated by SCS.
Checking Connections
If your SCS process starts, but clients cannot connect to an NonStop ODBC server, do
the following:
•
Check that there is network connectivity between the client and the NonStop
system, as described in the installation procedure. For example, if you are in a
Windows environment, you can use the HP Connectivity Tool.
•
Check that the client application is using the proper username or alias name and
has the proper password to connect.
Caution. If you have enabled OUTPUT_STREAM tracing for a session, do not issue a
SELECT of a log table during that session; this action causes the trace to enter an infinite loop
writing to the log table. Disable the trace by issuing a pass-through statement of the form
SELECT "tdm:set tra_mode_on n"
then select from the log table, or examine the log table using a different username, or use
SQLCI on the NonStop system.
34005 This error indicates that the SCS had a problem finding the network name
in the TCP/IP SERVICES file ($SYSTEM.ZTCPIP.SERVICES). Check to
make sure that the network name in the SERVICES file is all uppercase
and that it matches the name specified in the SCS configuration file. Also
check to make sure that the SERVICES file is located in the subvolume
$SYSTEM.ZTCPIP and that it has the proper file security to permit the
SCS process to read it.
34009 This error indicates that you tried to start SCS while running under an
improper user ID. You must start the SCS under another username.