User guide

For example:
SQS_MALIBU_SQLSRV_DIS06010.LOG
This log can be useful in determining why a dispatcher did not start up properly. For example
if appropriate logical names have not been setup as specified in the installation of Oracle
JDBC Drivers for Rdb then a message similar to the following may be found at the end of the
log file:
.
.
.
$ @rdb$jdbc_home:rdbjdbc_startsrv SQS1880 "SQS"
%DCL-E-OPENIN, error opening RDB$JDBC_HOME:[SYSMGR]RDBJDBC_STARTSRV.COM;
as input
-RMS-F-DEV, error in device name or inappropriate device type for
operation
SYSTEM job terminated at 21-JUL-2004 21:52:07.56
Accounting information:
Buffered I/O count: 37 Peak working set size: 2272
Direct I/O count: 14 Peak virtual size: 173072
Page faults: 192 Mounted volumes: 0
Charged CPU time: 0 00:00:00.04 Elapsed time: 0 00:00:00.21
7.1.4 Stopping a JDBC Dispatcher
The STOP DISPATCHER statement may be used to stop a running JDBC dispatcher.
Example
SQLSRV> STOP DISPATCHER JDBC_DISP
This will also stop the associated Oracle JDBC for Rdb server.
If you have associated the dispatcher with a pool server, and the pooled servers have
autoStart enabled, then these pooled servers will also be shut down at this time.
See your Oracle SQL/Services documentation for more information on the Oracle
SQL/Services management console.
Contents
7.2 Command Procedures used by Oracle SQL/Services
When a JDBC dispatcher is started, Oracle SQL/Services will use the OpenVMS command
procedure
103