Hi.

This is due to bug#128572.
Need upgrade TOOLS to 7.31.

HTH.
--
Tsutomu Ogiwara from Tokyo Japan.





>From: "Murray Wood" <Murray.Wood@integralgroup.co.nz>
>To: "Cats" <ramwater@uk2.net>, <informix-list@iiug.org>
>Subject: RE: isql/sperform/sacego and IDS 7.31
>Date: Fri, 1 Jun 2007 08:53:14 +1200
>
>
>You are using tools (ISQL etc) that were created prior to Solaris 8 or
>IPV6. The TCP libraries in 7.20 ISQL are not compatible with the
>Solaris 8. You must use Shared memory to connect from those tools to
>the engine.
>
>
>MW
>
>
>-----Original Message-----
>From: informix-list-bounces@iiug.org
>[mailto:informix-list-bounces@iiug.org] On Behalf Of Cats
>Sent: Friday, 1 June 2007 7:56 a.m.
>To: informix-list@iiug.org
>Subject: Re: isql/sperform/sacego and IDS 7.31
>
>On May 31, 7:38 pm, Richard Spitz <Richard.Sp...@med.uni-muenchen.de>
>wrote:
> > Cats <ramwa...@uk2.net> schrieb:
> >
> > >The problem is using the tools with a TCP connection to the database:
> > >/etc/services:
> > >v6new 1532/tcp # inhouse informix
> > >server
> > >v6newtcp 1533/tcp # inhouse informix
> > >server
> >
> > >$INFORMIXDIR/etc/sqlhosts:
> > >v6new onipcshm testhse2 v6new
> > >v6newtcp ontlitcp testhse2 v6newtcp
> > >dbaccess can happily connect to v6new and v6newtcp, but attempting to
> > >use any of the v7.20 tools against v6newtcp results in a -25572 error
> > >- "Network driver cannot bind a name to the port."
> >
> > Since "v6new" is defined as a shared memory connection, TCP/IP doesn't
> > play any role in this context.
>
>But it's v6newtcp it can't connect to - v6new is no problem for I/SQL.
>
> >
> > Have you made sure that port 1533 is not already in use by another
> > application or daemon?
>
>Would dbaccess be able to connect to it if it was?
>
> >
> > Can you try changing the entry for "v6newtcp" in your sqlhosts file
> > to the following:
> >
> > v6newtcp onsoctcp testhse2 v6newtcp
>
>Have a feeling I started with onsoctcp and had to alter it to what it
>is now due to what is and is not supported on that particular
>platform.
>
> >
> > Are server and application running on the same machine?
>
>Yes
>
> >
> > HTH, Richard
>
>
>_______________________________________________
>Informix-list mailing list
>Informix-list@iiug.org
>http://www.iiug.org/mailman/listinfo/informix-list
>_______________________________________________
>Informix-list mailing list
>Informix-list@iiug.org
>http://www.iiug.org/mailman/listinfo/informix-list

__________________________________________________ _______________
Web$B%Z!<%8$,ES@Z$l$:$KMQ;f$K$T$C$?$j0u:~$G$-$k$h$&$K$J$C$?:G?7%V%i%&%6(B
http://promotion.msn.co.jp/ie7/

On Jun 1, 2:05 am, "Ogiwara Tsutomu" <tsutomu_ogiw...@hotmail.com>
wrote:
> Hi.
>
> This is due to bug#128572.
> Need upgrade TOOLS to 7.31.
>
> >From: "Murray Wood" <Murray.W...@integralgroup.co.nz>
> >To: "Cats" <ramwa...@uk2.net>, <informix-l...@iiug.org>
> >Subject: RE: isql/sperform/sacego and IDS 7.31
> >Date: Fri, 1 Jun 2007 08:53:14 +1200
>
> >You are using tools (ISQL etc) that were created prior to Solaris 8 or
> >IPV6. The TCP libraries in 7.20 ISQL are not compatible with the
> >Solaris 8. You must use Shared memory to connect from those tools to
> >the engine.

I had a feeling that would be the case, was wanting to see someone
confirming it. Have had problems with V7.3x tools:

1) DBPATH was being truncated (the one bug I personally have found!)
2) the menu screens for lists of SQLs etc. didn't work properly.

I did have a bug number for #1 but have lost it, have never had one
for #2 and a browse through the online documentation at IBM hasn't
resolved these issues. In fact #1 probably isn't such an issue, but
#2 could be a show-stopper - it has been at other customers.

Any clues, anyone? Is there somewhere I can search the bugs online?