To use different DSQUERY names for each network listener:
Choose an additional server name.
You can concatenate the original server name and the network name. For example, if your server is named PRODUCTION, you could choose the names PRODUCTION_network1 and PRODUCTION_network2.
Do one of the following:
For PC clients, use sqledit to create multiple sql.ini file entries for the server, one for each network. In the following example, you create one entry for PRODUCTION_network 1 and one for PRODUCTION_network2. For more information, see the Open Client documentation for your client platform.
For UNIX clients, you can edit the interfaces files with an ASCII text editor. From the server’s interfaces files, copy the server name line and the “master” line for each network into the client interfaces file. Add the appropriate server name for each entry, and change “master” to “query.”
Clients on each network must use the DSQUERY value that corresponds to the network the client is on. In the following example, either PRODUCTION_network1 or PRODUCTION_network2 can be used.
# Client entry for PRODUCTION on network1 PRODUCTION_network1<tab>3<tab>3<newline> <tab>query tli tcp /dev/tcp \x0002130a83d601f60000000000000000 # Client entry for PRODUCTION on network2 PRODUCTION_network2<tab>3<tab>3<newline> <tab>query tli tcp /dev/tcp \x0002130a83d601f70000000000000000# Client entry for PRODUCTION on network1 PRODUCTION_network1<tab>3<tab>3<newline> <tab>query tcp ether zeppo 6464 # Client entry for PRODUCTION on network2 PRODUCTION_network2<tab>3<tab>3<newline> <tab>query decnet ether chico 150# Client entry for PRODUCTION on network1 PRODUCTION_network1<tab>3<tab>3<newline> <tab>query tcp ether serv_corpnet 4559 # Client entry for PRODUCTION on network2 PRODUCTION_network2<tab>3<tab>3<newline> <tab>query tcp ether serv_engnet 5479
