Re: dbservername/dbserveraliases/nettype

> MS CARLEEN C AVANT wrote: > > Looking for some guidance regarding the following: > > E4000, utilizing Solaris 2.6 and Informix 7.24.UC2 > > Following is the configuration: > > DBSERVERNAME sims4000_prod > > DBSERVERALIASES prod_tcp4000 > > SQLHOSTS: > > sims4000_prod onipchsm SIMS4000 prod_shm > > prod_tcp4000 ontlitcp SIMS4000 prod_tcp_svc > > Our problem: > > We have both shared memory connections and tcp connections to our server. > > We have identified the DBSERVERNAME for ipcshm connections and an alias for > > tlitcp connections. The problem we are now encountering is that the > > applications are all written to invoke the DBSERVERNAME, yet some of these > > applications are originating on another server and therefore are tlitcp > > connections and are consequently aborting when invoking the DBSERVERNAME. > > Not wanting to make numerous coding changes to reflect the alias name for > > those applications accessing the server via tlitcp, we were wondering if it > > is possible to have DBSERVERNAME as the alias name also (but as ontlitcp). On the client machine's sqlhosts file change the entry for sims400_prod to use tcp and the service used by the alias. Thus: SQLHOSTS on the client: sims4000_prod ontlitcp SIMS4000 prod_tcp_svc prod_tcp4000 ontlitcp SIMS4000 prod_tcp_svc The server does not listen for its name it only listens on a particular port so the listener on the server for alias prod_tcp4000 will see any connection requests from the client directed at the prod_tcp_svc port. BTW be careful to not use the same port for shared memory and tcp in the sqlhosts on the server (I know you do not but others are listening and need to be warned not to get lazy and try to use one sqlhosts file for both client and server, that goes for multiple servers that need to interact also). Do this and you are all set. Art S. Kagel