If uniform client DSQUERY naming is important, you can mask the necessary difference in the network addressing of the clients in the interfaces file. You can install separate Sybase installation directories and distinct interfaces files on client file servers on each network to allow users to connect to the correct network address. Instead of altering the DSQUERY name the clients use, you maintain one DSQUERY name for all clients, on all networks, and alter each network’s interfaces file accordingly.
This method assumes that:
You have complete control over what the Sybase installation clients see on each network.
The interfaces file (at the very least) is not shared or copied among Sybase installations on different networks.
The interfaces file would look like the following example on the “engineering” network:
#PRODUCTION server on network2 PRODUCTION<tab>3<tab>3<newline> <tab>query tli tcp /dev/tcp \x0002130a83d601f70000000000000000 <tab>master tli tcp /dev/tcp \x0002130a83d601f60000000000000000 <tab>master tli tcp /dev/tcp \x0002130a83d601f70000000000000000#PRODUCTION server network2<newline> PRODUCTION<tab>3<tab>3<newline> <tab>query decnet ether CHICO 150 <tab>master tcp ether ZEPPO 6464 <tab>master decnet ether CHICO 150# PRODUCTION server network2<newline> PRODUCTION<tab>3<tab>3<newline> <tab>query tcp ether SERV_ENGNET 5470 <tab>master tcp ether SERV_CORPNET 4559 <tab>master tcp ether SERV_ENGNET 5479
The “query” line in each file name is different, depending on the network to be used.
Using this method with UNIXWare, if the interfaces file examples shown in “Sample interfaces files for multiple network handlers” were adapted for this single DSQUERY method, they would look like the following example. The following example shows an interfaces file on the “corporate” network in a homogeneous UNIXWare environment:
#PRODUCTION server network1 PRODUCTION<tab>3<tab>3<newline> <tab>query tli tcp /dev/tcp \x0002130a83d601f60000000000000000 <tab>master tli tcp /dev/tcp \x0002130a83d601f60000000000000000 <tab>master tli tcp /dev/tcp \x0002130a83d601f70000000000000000#PRODUCTION server network1 PRODUCTION<tab>3<tab>3<newline> <tab>query tcp ether ZEPPO 6464 <tab>master tcp ether ZEPPO 6464 <tab>master decnet ether CHICO 150# PRODUCTION server network1 PRODUCTION<tab>3<tab>3<newline> <tab>query tcp ether SERV_CORPNET 4559 <tab>master tcp ether SERV_CORPNET 4559 <tab>master tcp ether SERV_ENGNET 5479
The full “master” entry is present in both files. This is allowed because only Adaptive Server will use the “master” lines. Assuming that the server host machine can see both networks (both host names are interchangeable), it does not matter which interfaces file is used for Adaptive Server start-up.
