Re: dbservername/dbserveraliases/nettype

"Scott Kolaya" <skolay1@nycap.rr.com> offerred: +>BTW be careful to not use the same port for shared memory and tcp in +>the sqlhosts on the server > +>Art S. Kagel +We've been using the same port for shared memory and tcp for a year now in +production. Yes, shared memory connections do not use a tcp/ip port, so the servicename is not actually used as a service name. That means you can use the same "servicename" for both one network connection and one shared memory connection within a single sqlhosts file. In fact, the "servername" acting as a "placeholder" in the shared memory connection entry is used as the basis for a filename, /INFORMIXTMP/.inf.XXXXXX (where XXXXX is the servicename you specified for the shared memory connection) that is used by clients accessing the server via the shared memory connection (the file contains a count of the number of shared memory poll threads running, among other stuff I forget now). So you can only use that "servicename" for one shared memory connection on a single Unix box. As far as I know, there are no gotchas with using the same service name for a network and shared memory connection other than the potential confusion it might engender. Dave Dave Kosenko davek@summitdata.com Director of Training Services (732) 469-4070 Summit Data Group (an Informix Authorized Education Center)