Am having a problem with isql on a SPARC Solaris 10 box.

If I load isql:
Software Serial Number RDS#N000000

The menu displays correctly:
IBM INFORMIX-SQL: Form Report Query-Language User-menu
Database ...
Run, Modify, Create, or Drop a form.
--------------------- lgh ---------------------- Press CTRL-W for Help
--------

If I select Form then Run (or Report then Run, or Query-Language then
Run) all previous versions have displayed a list of (respectively)
all the .frm files, the .arc files or the .sql files in the
directories listed in $DBPATH, and also from the cwd. None are being
listed.

With Query-Language, Run there is an error message:
SQL: New Run Modify Use-editor Output Choose Save Info Drop
Exit
Run the current SQL statements.
--------------------- lgh ---------------------- Press CTRL-W for Help
--------
823: There are no statements to run.

This doesn't happen with Form or Report.

If they type the name in manually it is fine - it finds and runs the
Form / Report / Query. $DBPATH looks to be set correctly.

Any clues, anyone?

BTW this is a new installation - the machine was wiped, Solaris 10
installed, then IDS11 and ISQL, then we restored the programs which
are Genero.

It has been over a decade since I used isql but I'm guessing the files
only show up when your run isql in the same directory where the files
exist.

Otherwise it might be an isql bug on Solaris 10.

-LS

It's probably a known bug in the client SDK that was used to compile that
version.
Installing a more recently version of ClientSDK could solve that but I've
seen reports that may lead to others.
7.50.FC5 should be already available, or if not FC3 will solve your problem.
For more details please contact tech support through a PMR.

Regards.

On Thu, May 12, 2011 at 5:15 PM, Cats <ramwater (AT) uk2 (DOT) net> wrote:



--
Fernando Nunes
Portugal

http://informix-technology.blogspot.com
My email works... but I don't check it frequently...

On May 12, 11:23*pm, Fernando Nunes <domusonl... (AT) gmail (DOT) com> wrote:
I have also taken this up with the chap that provided the download for
me. The Client SDK isn't installed on the machine we have this
problem on. Asking here was a long shot incase anyone had had the
problem.

But thanks to all.

On May 13, 7:36*am, Cats <ramwa... (AT) uk2 (DOT) net> wrote:
OK, it was a problem with the CSDK it was compilled with, and since I
downloaded that version a newer one has come along that has fixed the
problem.