Informix 4.10.UE2 (SCO) + linux-abi = 922: Cannot get name of current working directory

Howdy folks - I'm at a loss on this one. I have a copy of "INFORMIX-SQL Version 4.10.UE2", originally installed on a SCO 3.2v4 machine, dumped onto a Linux machine running 2.6.11 (and the 2.6.11-rc1 linux-abi kernel patches). When I run "dbaccess" and create a new database, it appears to work just fine, creating about 39 files under the new database directory (ie: syschecks.idx, syscolauth.dat, syscolauth.idx, etc, etc.). When I try to *select* the database I've just created using dbaccess, I get the error message: 922: Cannot get name of current working directory. ...which is strange, because it just created the various system tables, right? This happens regardless of where I run "dbaccess" on the system (even under /tmp, for example) - I'm guessing it's some kind of library problem, but there's no way to strace / truss this thing because it's a SCO binary... I'd read somewhere that this error might be reported when dbaccess/sqlexec/isql tries to run a non-existent helper command on the system (kind of a bogus error message that indicates some other underlying problem). Thanks in advance for any tips out there! Robert Giles (I also see this error message on a SCO OSR 5.0.7 box when I try to load my database as "root", but not as the regular DB user??? But at least "dbschema" and friends work while running as the DB user - so it could possibly be exported to a newer Linux version of Informix)

Robert Giles wrote: > Howdy folks - I'm at a loss on this one. > > I have a copy of "INFORMIX-SQL Version 4.10.UE2", originally installed > on a SCO 3.2v4 machine, dumped onto a Linux machine running 2.6.11 > (and the 2.6.11-rc1 linux-abi kernel patches). I4GL 4.10 - circa 1989, 1990 at the latest. Probably built on SCO Xenix rather than SCO Unix, probably for a 386, maybe a 486 if you're lucky. > When I run "dbaccess" and create a new database, it appears to work > just fine, creating about 39 files under the new database directory > (ie: syschecks.idx, syscolauth.dat, syscolauth.idx, etc, etc.). > > When I try to *select* the database I've just created using dbaccess, > I get the error message: > > 922: Cannot get name of current working directory.> > ...which is strange, because it just created the various system > tables, right? It depends on how the code determines the current directory. There's a moderate chance it tries to read the directory, expects it to be a old-style Unix file system - old, meaning not more than 14 characters in the file name, all entries 16 bytes long, the other 2 bytes being the inode number, etc. Are you running on that type of file system? > This happens regardless of where I run "dbaccess" on the system (even > under /tmp, for example) - I'm guessing it's some kind of library > problem, but there's no way to strace / truss this thing because it's > a SCO binary... > > I'd read somewhere that this error might be reported when > dbaccess/sqlexec/isql tries to run a non-existent helper command on > the system (kind of a bogus error message that indicates some other > underlying problem). > > Thanks in advance for any tips out there! Frankly, it is time to put the poor old build out of its misery - and upgrade to something released a decade or more later. > (I also see this error message on a SCO OSR 5.0.7 box when I try to > load my database as "root", but not as the regular DB user??? But at > least "dbschema" and friends work while running as the DB user - so it > could possibly be exported to a newer Linux version of Informix) Isn't it amazing how well programs that are 15+ years old work despite all the changes. There wasn't a world-wide web when it was released! -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/