User guide

8.14 On Start Commands
There are two startup command attributes that may be specified in the XML-formatted
configuration file server section: srv.onStartCmd and srv.onExecStartCmd.
These options allow the specification of DCL command that should be executed just prior to
the start up of a server or executor.
Note:
The srv.onStartCmd and the srv.onExecStartCmd point to a command that will be execute on
start up of the server or executor. If the command is to invoke a DCL command procedure
you must also include the DCL invocation symbol @ in the command line.
8.14.1 srv.onStartCmd
This option specifies a DCL command to be executed prior to the invocation of the specified
thin server. It must be a valid OpenVMS DCL command and must be valid within the
context of the server process created by the controller or pool server.
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
controller or pool server runs. Oracle recommends that these command procedures be placed
within the rdb$jdbc_com directory and the file protection set to allow the controller or pool
server execute access.
Example 1
For example, if your system requires a specific setup to be run to set your Java environment
and Oracle Rdb environment, you may create a command procedure similar to the following
example.
Create rdb$jdbc_com:our_setup.com containing
$@sys$share:rdb$setver 71
$@sys$common:[java$141.com]JAVA$141_SETUP.COM
and provide a pointer to this command procedure in the srv.onStartCmd option
<server
name="srv2forRdb"
type="RdbThinSrv"
url="//localhost:1708/"
122