User guide

rdb$jdbc_home:rdbjdbc_startsrv.com
and the executor startup command procedure:
rdb$jdbc_home:rdbjdbc_startexec.com
Caution:
Do not use the SET VERIFY command within these command procedures. As the method
Runtime.exec() may be used by the servers to create processes, the use of the SET VERIFY
command within the command procedure may hang the server. This is a documented
limitation of using Runtime.exec() on Open VMS Java. The logical name
JAVA$EXEC_TRACE is available to help debug Runtime.exec() calls on OpenVMS. Refer
to the OpenVMS Java documentation for more details.
Note:
If the only changes required are environmental setup, Oracle recommends that instead of
altering the start-up command procedures, the server attribute srv.onStartCmd or
srv.onExecStartCmd should be considered. See On Start Commands
for more details.
8.18.1 Server Startup Command Procedure
The controller uses the server startup command procedure to start a thin server.
The
srv.startup option within the server section of an XML-formatted configuration file
may be used to specify the file specification of the command procedure that should be used
to start that server.
<server
Example
For example:
name="srv2forRdb"
type="RdbThinSrv"
url="//localhost:1708/"
autoStart="true"
logfile=rdb$jdbc_logs:srv2forRdb.log"
srv.startup="rdb$jdbc_com:our_customized_startsrv.com"
/>
During the driver kit installation the command procedure
rdbjdbc_startsrv.com is placed
in the rdb$jdbc_home directory. This file will be used by default for server start up using the
controller and pool servers.
The DEFAULT server provided in the default configuration file rdbjdbccfg.xml specifies this
command procedure.
130