User guide

srv.startup=rdb$jdbc_home:rdbjdbc_startsrv.com
You can choose to change this default command procedure to customize for your system
settings, or you can create a new customized procedure and change the configuration file so
that servers use this new file. However Oracle recommends that you use the srv.onStartCmd
server attribute instead. See srv.onStartCmd
for more information on using the
srv.onStartCmd attribute.
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:
The server startup command procedure is only used by the controller or pool server to start a
thin server, if the server is started by any other means neither the server startup command
procedure nor any commands in the srv.onStartCmd server attribute will be executed.
8.18.2 Executor Startup Command Procedure
The thin multi-process server uses the executor startup command procedure to start an
executor process for a client connection.
You can use the
srv.execStartup option to specify the file specification of the command
procedure that should be used to start executors by a multi-process server.
Example
For example:
<server
name=MPsrv2forRdb
type=RdbThinSrvMP
url=//localhost:1788/
srv.execStartup=rdb$jdbc_com:our_customized_startexec.com
/>
You can choose to change this default command procedure to customize for your system
settings, or you can create a new customized procedure and change the configuration file so
that servers use this new file. However Oracle recommends that you use the
srv.onExecStartCmd server attribute instead. See srv.onExecStartCmd
for more information
on using the srv.onExecStartCmd attribute.
131