ODBC Server Reference Manual

Managing Customized Catalogs
HP NonStop ODBC Server Reference Manual—429151-002
7-102
SQL Communications Subsystem (SCS) Statements
STOP SCS
The STOP SCS statement stops an SCS process. To execute STOP SCS, you must
be a privileged user.
scs-processname
specifies the process name of the SCS process you want to stop.
The SCS process stops when system configuration values are next updated. The
NonStop ODBC Server gracefully shuts down each server process in each server
class defined for scs-processname (that is, each server process continues
running until the respective client session ends).
NOWAIT
causes the SCS process to stop immediately.
Considerations – STOP SCS
The STOP SCS statement generates an error if scs-processname does not exist in
the ZNSSCS table, if NOSUTIL is unable stop the SCS process, or if you are not a
privileged user.
To determine whether an SCS process is stopped, do not rely on the SCS_STOPPED
flag (which is displayed by the INFO SCS statement). SCS_STOPPED does not
necessarily indicate whether an SCS process has actually stopped. Instead, use the
NOSCOM STATUS SCS scs-processname statement or the TACL STATUS
scs-processname command.
SCS_STOPPED is an internal flag used for the graceful shutdown of SCS. If the SCS
process is stopped, SCS_STOPPED can have these meanings:
•
If SCS_STOPPED is Y, the previous instance of the SCS process was stopped
gracefully (unless you stopped the process with a NOSCOM STOP SCS statement
followed by a TACL STOP command).
•
If SCS_STOPPED is N, the previous instance of the SCS process was not stopped
gracefully.
Example
STOP SCS $myscs NOWAIT
STOP SCS scs-processname [ NOWAIT ]