On Win32 platforms:
[startup]
1=tcpw.w32 -distributed -server_name
servername
2=dp4srvr.w32 -distributed
On Windows CE platforms:
[startup]
1=tcpw.wce -distributed -server_name
servername
2=dp4srvr.wce -distributed
On Unix and Linux:
tcp3 -distributed -server_name
servername
-remain
srv3 -distributed -remain
If you are using 4.525 and dbdaemon you would use this startup section instead:
[startup]
1=tcp3 -distributed -server_name
servername
2=srv3 -distributed
On MS-DOS:
tcp2 -distributed -server_name
servername
-remain
srv2 -distributed -remain
In each case servername is replaced by the pingable name of the DP4 server machine. As before you can load DP4 temporarily. The -remain command tail must be omitted everywhere. On Windows add the -noremain option to the startup line for either or both dp4srvr.w32 and tcpw.w32 (it does not matter which.)
The order of the commands given above is in fact usually interchangeable. However, you are recommended to adhere to the order given above, as it is the only one officially supported on all platforms.
In a local resilience configuration there are a number of special options which determine the behaviour of the system in the event of a network error. These Resilience Command Tails are supplied to the database manager (e.g. srv3 or dp4srvr.w32), and not to the network programs. Without one of the Resilience Command Tails, if the server or the link to it fails, the application terminates with an error message.
Programs such as DBBACKUP and DBRESTOR, when run on a client, work on the local database and not on the remote database. However, if the command tail −readlocal is supplied to the database manager on the client instead of −distributed , then these programs work on the remote database. −readlocal is used only on the database manager - you always use −distributed when loading the network requester in local database resilience mode.
Please note the highly misleading name of this command tail: −readlocal actually means read remote!
Where more than one server is in use it is possible (and except for TCP/IP mandatory), to select the server not by specifying a value for -server_name, but instead specifying -server n , where n is a number between 1 and 65535 for TCP/IP, or 1 and 9999 for NetBIOS. In the local resilience configuration the -server N command tail is specified on the database manager (srv3,dp4srvr.w32) and not on the network requester.
For example, on Unix and Linux:
tcp3 -distributed -remain
srv3 -distributed -remain -server
N
For further information refer to the section on server numbers.
If you use this method to select the server, applications will not be able to select a different server using the -server_name command tail.