ASA Database Administration Guide
The Database Server
The database server
Database server options
To specify server side network communications protocols.
dbsrv9 -x { all | none | srv-protocols } ...
srv-protocols:
{ [ namedpipes | spx | tcpip ] parmlist },...
parmlist:
( parm=value;...)
dbeng9 -x { all | none | eng-protocols } ...
eng-protocols:
{ namedpipes | tcpip [ parmlist ] },...
parmlist:
( parm=value;...)
All operating systems and servers.
Use the -x option to specify which communications protocols, in addition to shared memory, you want to use to listen for client connection broadcasts.
If you do not specify the -x option, the server attempts to listen for client connection broadcasts using all protocols supported by the database server running on your operating system, including shared memory.
If you specify the -x option with one or more protocols, the server attempts to listen for client connection broadcasts using the specified protocol(s) and also using a shared-memory protocol.
If you are running Windows CE and specify the |
Regardless of which settings you choose for the -x option, the server always listens for connection broadcasts using the shared memory protocol. In addition to the shared memory protocol, you can also specify the following:
ALL Listen for connection attempts by the client using all communications protocols that are supported by the server on this platform, including shared memory. This is the default.
NamedPipes (NP) Listen for connection attempts by the client using the NamedPipes protocol. NamedPipes is supported on Windows NT/2000/XP as an alternative means of same-machine communication.
NONE Listen for connection attempts by the client using only the shared memory protocol.
SPX Listen for connection attempts by the client using the SPX protocol. The SPX protocol is supported by NetWare, Windows NT/2000/XP, and Windows 95/98/Me network servers.
TCPIP (TCP) Attempt to connect to the client using the TCP/IP protocol. The TCP/IP protocol is supported by the network server on all operating systems, and by the personal database server for same-machine communications.
By default, the database server listens for broadcasts on port 2638, and redirects them to the appropriate port. This ensures a connection in most cases. You can override this default and cause the server not to listen on port 2638 by setting the option -sb 0, or by turning off the BroadcastListener option (BroadcastListener=0). Additionally, if the client and server are communicating through a firewall, the client must send the packet to the exact port the server is listening on by specifying DoBroadcast=None and Host=. |
For information, see ServerPort communication parameter [PORT].
For some protocols, additional parameters may be provided, in the format
-x tcpip(PARM1=value1;PARM2=value2;...)
For a description of available parameters, see Network communications parameters.
For UNIX, quotation marks are required if more than one parameter is supplied:
-x "tcpip(PARM1=value1;PARM2=value2;...)"
Allow only shared memory, TCP/IP and SPX communications:
-x tcpip,spx
CommLinks connection parameter [LINKS]