RE: Installing Client SDK - 32 bit (64 bit IDS) NIGHTMARE
Greetings, > 3) What about using a separate 32 bit machine as a client to > take all of the > 64 bit headache out of it, possibly even a windows machine > (don't tell anyone > I said that) That is what I did. This is my setup - on Solaris: 1. The 64 bit version installed here - $INFORMIXDIR = /opt/informix/ids_9.40.FC3; INFORMIXDIR should point to the 64 bit installation. 2. Install the 32 bit version of the SDK on the same machine; however, make sure it is installed in a different directory: /opt/informix/ids_9.40.UC3 3. Use /opt/informix/ids_9.40.UC3/lib as your link directory Mike Badar ESRI 1 International Court Broomfield, CO 80021-3200 303-449-7779 mbadar@esri.com www.esri.com
Mike A -" Why not connect to both sources using unixodbc ? " Well I get the same problem there. The CISAM driver, by necessity is 32 bit. My Informix db is 64 bit. Re getting a second machine - yes that's a possibility. But I must have the Cisam files on the IBM/LINUX machine as they are produced by software which will not run on another platform. I have the informix db on the same machine. If I use two machines then it seems a waste of processor power and network resources. Kate Anyway now I have NO SDK. It will not install!@
kjuliff@gmail.com wrote: > Mike A -" Why not connect to both sources using unixodbc ? " > > Well I get the same problem there. The CISAM driver, by necessity is 32 > bit. My Informix db is 64 bit. You may have a 32-bit client talking to 32-bit database servers; you may have 64-bit clients talking to 64-bit database servers; you may also have 32-bit clients talking to 64-bit database servers and 64-bit clients talking to 32-bit database servers. The only restriction on the combinations are (a) the client must be all 32-bit or all 64-bit and not a mixture, and (b) a 32-bit client cannot use a shared memory connection to a 64-bit database server, nor can a 64-bit client use a shared memory connection to a 32-bit database server. (Those who know about HP-UX and the HCx versions, please keep quiet - you'll confuse things.) So, as Mike Badar and Mike Aubury both implied, and as I've tried to say before too, what you need to do is install a 32-bit CSDK on your machine in a different directory (different INFORMIXDIR) from the 64-bit IDS (and the 64-bit CSDK that you might have installed in the 64-bit IDS INFORMIXDIR). When you compile and run your mixed ESQL/C + UnixODBC application, compile in 32-bit all the way, using the compiler and libraries. At run time, you will run the mixed application with the environment pointing to the 32-bit INFORMIXDIR (and 32-bit UnixODBC); the only thing that points to the 64-bit software will be the entry in the sqlhosts file that identifies the 64-bit version of IDS. > Re getting a second machine - yes that's a possibility. But I must have > the Cisam files on the IBM/LINUX machine as they are produced by > software which will not run on another platform. > > I have the informix db on the same machine. > > If I use two machines then it seems a waste of processor power and > network resources. Two machines are not necessary, but you do need two separate INFORMIXDIR locations on the single machine. > Anyway now I have NO SDK. It will not install!@ Make sure you have the correct 32-bit CSDK for the platform you have. I think you said it is an IBM xSeries running RHEL4? Is that Itanium or EM64T or AMD or something else? This may control whether you can obtain a 32-bit CSDK that works on your machine. Since you've not 'fessed up to exactly what hardware or software you have, AFAICT, we can't help you more precisely. People have been trying to dig that information out of you - I find it hard to believe it is a state secret that cannot be revealed. -- Jonathan Leffler #include <disclaimer.h> Email: jleffler@earthlink.net, jleffler@us.ibm.com Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/