User guide

Alternatively, you may wish to create a server definition within an XML-formatted
configuration file and then start the server using its server name. Again the server type
must be set to RdbThinSrvMP.
Given the following server section in the XML-formatted configuration file mycfg.xml:
<server
name="Mpserv1"
type="RdbThinSrvMP"
url="//localhost:1799/"
sharedmem="102400"
logfile="myLogs:serv1.log"
/>
the following method may be used to start this multi-process server:
$ java –jar rdbthinsrv.jar –cfg mycfg.xml –name Mpserv1
3.2.2 Shared Memory Usage
The multi-process server needs to allocate shared global memory for communication with
its executors, which you may specify using the sharedmem server configuration option.
The default allocation for shared memory is 1024 KB and is only adequate for one or two
executors.
A rule of thumb that can be used is to allow 1024 KB for each concurrent executor you
expect to be running in conjunction with the server, but this will depend on the complexity
of the queries, the number of columns involved and the size of the data area that will have
to be created to hold the data returned to the executor by Rdb.
3.2.3 Prestarted Executors
With a multi-process server you may also specify the number of executor process that may
be prestarted when the server starts running.
In addition you can also specify the maximum number of free executor process that may be
kept around while the server is running. This is particularly useful if your system takes a
while to start OpenVMS processes and sub-processes due to system load.
By prestarting executor processes you may reduce the overall elapsed time it takes for a
client to make its initial database connection.
24