User guide

This subsection specifies the usernames the server will allow access to. The declared
username must be a valid username recognized by Rdb. The matching of usernames by the
server for this level of restriction is not case-sensitive.
The subsection is only valid when used within a server declaration
.
Multiple AllowUser subsections may be present in a single server declaration.
For user access to be restricted the server attribute
restrictAccess must be set "true".
See the section Restricting User Access
for more details
Format
<allowUser name="username" />
Example
<server
name="srv2restrict"
type="RdbThinSrv"
url="//localhost:1701/"
restrictAccess="true">
<allowUser name="smith"/>
<allowUser name="jones"/>
</server>
4.3.2.10 Using filenames in the configuration file
A number of attributes within the configuration file sections require the specification of a
filename, for example:
 cfg="<filename>"
 log="<filename>"
 srv.execStartup="<filename>"
 srv.startup="<filename>"
The filename must be a valid OpenVMS file specification that may contain a full or partial
file path and may include logical names.
You must ensure that, if logical names are used, they are available to the context within
which the server will be started, and that the file is accessible by the VMS user that starts
up the server.
If a server defined in the configuration will be started up using the controller, as a pooled
server by a pool server, or by Oracle SQL/Services, a detached process will be created for
the server and the LOGINOUT.EXE will be run to ensure a valid process environment
under which Java and Oracle Rdb can be accessed.
54