Manage One Network-Independent DSQUERY Name

You can maintain one DSQUERY name for all clients, on all networks, and alter each network’s interfaces file accordingly.

If uniform client DSQUERY naming is important, you can make the necessary changes in the network addressing of the clients in the interfaces file. You can install separate SAP 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 SAP installation clients see on each network.
The interfaces file (at the very least) is not shared or copied among SAP installations on different networks.

The interfaces file looks like this on the “engineering” network:

 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 interfaces file looks like this example on the “corporate” network:

 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 “query” line in each file name is different, depending on the network to be used.

The full “master” entry is present in both files. This is allowed because only SAP ASE uses 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 SAP ASE start-up.