Hi,

I am hoping some Informix expert can give me some info on this. I
have setup shared memory connection for informix. After I connected
to the database using shared memory, is there a way to verified what I
connected. Like may be some database views or tables that show the
information. My sqlhosts is setup like this.

in0pheas ontlitcp pheasant nettcp3
il0pheas ontlitcp pheasant nettee
is0pheas onipcshm pheasant sqlexec

is0pheas is the one that is setup for shared memory.

Thanks for any help.
Louis.

Louis-
Assuming you connected with dbaccess or isql, look just below
the ring menu after you connect to a database. It should read something
like:

-------------mydatabase@myserver--------------

If myserver = is0pheas, then you have a shared memory connection. Also,
if your connecting through 4GL and your $INFORMIXSERVER is is0pheas and
you don't have to change servers when you connect, you are connecting to
shared memory on is0pheas. If you are connecting another way, you need
to specify what you're using for a better answer.

--EEM

> -----Original Message-----
> From: informix-list-bounces@iiug.org [mailto:informix-list-
> bounces@iiug.org] On Behalf Of louis.lam@guardium.com
> Sent: Friday, May 18, 2007 10:39 AM
> To: informix-list@iiug.org
> Subject: how to I know I am connected to shared memory.
>
>
> Hi,
>
> I am hoping some Informix expert can give me some info on this. I
> have setup shared memory connection for informix. After I connected
> to the database using shared memory, is there a way to verified what I
> connected. Like may be some database views or tables that show the
> information. My sqlhosts is setup like this.
>
> in0pheas ontlitcp pheasant nettcp3
> il0pheas ontlitcp pheasant nettee
> is0pheas onipcshm pheasant sqlexec
>
> is0pheas is the one that is setup for shared memory.
>
> Thanks for any help.
> Louis.
>
> _______________________________________________
> Informix-list mailing list
> Informix-list@iiug.org
> http://www.iiug.org/mailman/listinfo/informix-list

louis.lam@guardium.com wrote:
> I am hoping some Informix expert can give me some info on this. I
> have setup shared memory connection for informix. After I connected
> to the database using shared memory, is there a way to verified what I
> connected. Like may be some database views or tables that show the
> information. My sqlhosts is setup like this.
>
> in0pheas ontlitcp pheasant nettcp3
> il0pheas ontlitcp pheasant nettee
> is0pheas onipcshm pheasant sqlexec
>
> is0pheas is the one that is setup for shared memory.

How are you connecting? Which language are you using?

Connection failures return any of a large variety of errors, and most
likely you'd see one unless you studiously ignore them. If you want to
be sure, you could try selecting data from the system catalog:

SELECT owner, tabname FROM "informix".systables WHERE tabid = 1;

Should return owner = "informix" and tabname = "systables".

--
Jonathan Leffler #include <disclaimer.h>
Email: jleffler@earthlink.net, jleffler@us.ibm.com
Guardian of DBD::Informix v2007.0226 -- http://dbi.perl.org/

Thank you for all your reply, I have found the solution from another
user email to me. It is

onstat -g ntu

Work good for me, I can identified the session and see the type of
connection. I am using DBACCESS.

louis.lam@guardium.com wrote:
> Hi,
>
> I am hoping some Informix expert can give me some info on this. I
> have setup shared memory connection for informix. After I connected
> to the database using shared memory, is there a way to verified what I
> connected. Like may be some database views or tables that show the
> information. My sqlhosts is setup like this.
>
> in0pheas ontlitcp pheasant nettcp3
> il0pheas ontlitcp pheasant nettee
> is0pheas onipcshm pheasant sqlexec
>
> is0pheas is the one that is setup for shared memory.
>
> Thanks for any help.
> Louis.

If you want to be able to verify your connection from outside that session,
you can, presumably from another session, do:

select *
from syssessions
where uid = 'client user id' and pid = <client pid> and hostname = 'client
host';

Art S. Kagel