User guide

8.14.2 srv.onExecStartCmd
This option specifies a DCL command to be executed prior to the invocation of an executor
by a multi-process server. It must be a valid OpenVMS DCL command and must be valid
within the context of the multi-process server process.
If multiple DCL commands are required, then they should be placed within a DCL command
procedure, which in turn should be made available to the environment under which the server
runs. It is recommended that these command procedures should be place within the
rdb$jdbc_com directory and the file protection set so that the server can access them.
Example
For example, if your system requires a specific setup to be run to set your Oracle Rdb
environment, you may create a command procedure similar to the following example.
Create rdb$jdbc_com:our_exec_setup.com containing
$@sys$share:rdb$setver 7.1
and provide a pointer to this command procedure in the srv.onExecStartCmd option
<server
name="MPsrv2forRdb"
type="RdbThinSrvMP"
url="//localhost:1788/"
srv.onExecStartCmd="@rdb$jdbc_com:our_exec_setup.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.
Contents
8.15 Password Obfuscation in Server Configuration Files
To prevent an unauthorized user from controlling server operations such as closing down a
running server, a control password should be assigned to each server on startup.
This password must be used whenever server control operations are carried out using the
Oracle JDBC for Rdb Controller interface.
124