The easiest way to load the TCP/IP client software is as follows:
On Windows clients use the following [startup] section in the DP4 configuration file.
[startup]On Windows CE clients use the following [startup] section in dp4.ini.
[startup]On Unix and Linux use the following command in a shell or a
shell script:
tcp3 -remain -server_name servername
If you are using 4.525 and dbdaemon, use the following command in the [startup] section of dp4.ini
1=tcp3 -server_name servername
The -remain command tail is not used with release 4.525, whether or not dbdaemon is used to load DP4.
On MS-DOS use the following command at the prompt or in a batch
file:
tcp2 -remain
In each case servername should be replaced by the name you use to ping the machine where tcpmgr and the DP4 server will run. From version 4.621 servername may also be given as #<ip_address> e.g. #192.168.160.12 . This is primarily intended for creating "reverse" connections in the named server DP4 configuration, and is not recommended for normal use. The -server_name command tail is not available on MS-DOS.
The commands given above cause the DP4 requester to remain loaded permanently. It is possible to load the requester so that it unloads after the last DP4 program has terminated (the requester will remain loaded in any case until at least one DP4 program has been run). To do this omit the -remain command tail on MS-DOS and Unix/Linux (4.523). On Windows (or Windows CE), or 4.525 Linux/Unix add -noremain to the [startup] line for the tcpw/tcp3
Batch files, or the Linux/Unix shell (though not dbdaemon), will automatically replace variables such as %server_name or $servername (as appropriate to the platform) with the value of the variable as defined in the environment. This can be a very convenient method of avoiding having to generate separate configuration scripts for each site. Although the Win32 tcpw is not loaded from a script, the tcpw program itself will use the environment to replace a servername beginning with a % sign with the value of the corresponding environment variable. (Don't put a trailing % sign at the end of the name in this case.)
This is not the case for Unix/Linux programs loaded by dbdaemon. If you want to use dbdaemon, and take advantage of environment variable
options, make dbdaemon invoke a shell script rather than a DP4 command directly.
For example:
[startup]
1=sh dp4start
dp4start might contain the following command:
tcp3 -server_name $DP4SERVER
If tcp3, or any other DP4 component, is loaded like this, it will run exactly as though it had been started directly from dbdaemon, and dbdaemon -stop will still unload it. Rather than invoking sh explicitly you may prefer to make your script executable using chmod +x. If you do this the line 1=dp4start will work perfectly well.
You may also be able to configure your DNS server to translate one name to another by adding a CNAME, or alias, record to its database.
If you do not specify the -server_name option the tcp requester will look for a server called dp4server.
The -server_name option was introduced in version 4.520 and is only available with TCP/IP networking. It is not available for other protocols or with earlier releases of DP4 TCP/IP networking.
All DP4 networking programs (both clients and managers) accept a command tail of the form -server N where N is a number. In a way that varies depending on the protocol and platform, network requesters will locate the correct network manager to use by discovering the network manager with the desired server number. See the section on server numbers for more information.