Re: NETTYPE and sqlhosts workings

In article <38F1FB40.793B7E99@ndr.com>, allenj <allenj@ndr.com> wrote: > The facts: IDS 7.31.UC2 on HP K260 w/ HP-UX 10.20 > > If I have the following in my $ONCONFIG: > NETTYPE ipcshm,2,75,CPU > NETTYPE soctcp,2,75,NET> > But only have the following in my sqlhosts file: > ndrmain onsoctcp ndrmain sqlexec Revise the above entry to as follows: ndrmain_shm onipcshm ndrmain sqlexec ndrmain_soc onsoctcp ndrmain sqlexec2 The idea is to define one entry for the shared memory and one for sockets. Make sure you have defined sqlexec2 as a service in /etc/services. from your posting I gather that sqlexec is already defined. Prior creating a new entry in /etc/services make sure that the port number that you are about to allocate is not used elsewhere by other applications. > > Does this mean that my server will only handle socket connections, and > not shared mem connections? Does the $ONCONFIG NETTYPE ipcshm line make > the server handle shared mem connections even though the sqlhosts file > does not specify ipcshm? Do I need to add another line to the sqlhosts > file for shared mem? > > The doc mentions creating a DBSERVERALIAS for my DBSERVERNAME, and then > using that alias in sqlhosts for onipcshm connections. Why would I want > to use an alias for shmem connections? Its simple: If a client app is > running local, use shmem. If its running across the n/w, use a n/w > connection. In the config file make sure that the DBSERVERNAME points to the shared memory and the DBSERVERALIAS points to the socket connection. > > Am I trying to read too much into this? > > Thanks for any help > > Allen > Thanks Ram S. Sent via Deja.com http://www.deja.com/ Before you buy.

ram_cnc wrote: > In article <38F1FB40.793B7E99@ndr.com>, > allenj <allenj@ndr.com> wrote: > > The facts: IDS 7.31.UC2 on HP K260 w/ HP-UX 10.20 > > > > If I have the following in my $ONCONFIG: > > NETTYPE ipcshm,2,75,CPU > > NETTYPE soctcp,2,75,NET> > > > But only have the following in my sqlhosts file: > > ndrmain onsoctcp ndrmain sqlexec> > Revise the above entry to as follows: > > ndrmain_shm onipcshm ndrmain sqlexec > ndrmain_soc onsoctcp ndrmain sqlexec2> > The idea is to define one entry for the shared memory and one for > sockets. > > Make sure you have defined sqlexec2 as a service in /etc/services. from > your posting I gather that sqlexec is already defined. [SNIP] > > Thanks > > Ram S. > > Sent via Deja.com http://www.deja.com/ > Before you buy. Excuse me Ram, but the Informix server will ignore the "service" field of entries in the "sqlhosts" file whose "protocol" field is "onipcshm". Therefore, in the above example, "sqlexec" can be used in the entry with "onsoctcp" in the "protocol" field. Cheers, Avi. -- /\\ \\ /| Avi Abrami, Analyst/Programmer, Terayon Comms /__\\ \\ / | eMail: avia@terayon.com / \\ \\/ | http://www.terayon.com

Avi Abrami wrote: > ram_cnc wrote: > > > In article <38F1FB40.793B7E99@ndr.com>, > > allenj <allenj@ndr.com> wrote: > > > The facts: IDS 7.31.UC2 on HP K260 w/ HP-UX 10.20 > > > > > > If I have the following in my $ONCONFIG: > > > NETTYPE ipcshm,2,75,CPU > > > NETTYPE soctcp,2,75,NET> > > > > > But only have the following in my sqlhosts file: > > > ndrmain onsoctcp ndrmain sqlexec> > > > Revise the above entry to as follows: > > > > ndrmain_shm onipcshm ndrmain sqlexec > > ndrmain_soc onsoctcp ndrmain sqlexec2> > > > The idea is to define one entry for the shared memory and one for > > sockets. > > > > Make sure you have defined sqlexec2 as a service in /etc/services. from > > your posting I gather that sqlexec is already defined. > > [SNIP] > > > > > Thanks > > > > Ram S. > > > > Sent via Deja.com http://www.deja.com/ > > Before you buy. > > Excuse me Ram, but the Informix server will ignore the "service" > field of entries in the "sqlhosts" file whose "protocol" field is > "onipcshm". Therefore, in the above example, "sqlexec" can be used > in the entry with "onsoctcp" in the "protocol" field. WELLLLL almost. You MUST NOT use the same service name for the shared memory entry in sqlhosts as you do for ANY other entry for the SAME server. If you do the server will begin polling that service which will spin the CPUs and generate thousands of unneeded system calls per second. You are correct that the service name used for shared memory connections does not need to be in /etc/services it is a dummy and can be anything, however, as I said it must not be the same as that used by another protocol on the same service. Personally I always enter the shared memory servicename in /etc/services anyway, it cannot hurt. Art S. Kagel