Popular White Paper On This Topic

To continue, I have found and downloaded the Data Server client, which contains The IBM? Data Server Driver for ODBC, CLI, and .NET . I installed this - with a db2setup command - but the Perl "make" get the same error message about various constants not found
Constants.xs:16:20: error: sqlcli.h: No such file or directory
Constants.xs:18:21: error: sqlcli1.h: No such file or directory
Constants.xs:19:20: error: sqlext.h: No such file or directory
Now, the install generated a different directory, /opt/ibm/db2/V9.5_01 for the code, vs. the V9.5 directory which contains DB2 Express-C. I wasn't sure if I wanted to "over-write" it, and so let it do its own thing.
Maybe this was wrong?
Perhaps I should uninstall the DS client, and let it go to the /opt/ibm/db2/V9.5 directory?
I just don't want to jeopardize an existing installation into which I have put a lot of work.
Thanks
wombat53

Further to this, according to an old DB2 Magazine article on this subject in 2005 at:
http://www.ibmdatabasemag.com/showArticle.jhtml?ar ticleID=59301551, it is said the DB2 run-time client is required (I have Express-C V9.5.0, Fedora 9 Linux). I have installed the more modern Data Server Driver for ODBC and CLI, a subset of the Data Server runtime client (carefully followed the manual install instructions).
Still I cannot do the Perl "make", with these 3 files not being found *sqlcli.h, sqlcli1.h and sqlext.h.
So, I come back to installing the runtime client, which is a full GUI launchpad installation. When I have tried this it suggests a different directory for install, other than /opt/ibm/db2/V9.5...it is..../V9.5_01, which I selected , and no change: the Perl make still fails.
So, my question is: can/should I install the runtime client into the SAME directory path as the Server (Express-C)????? Hopefully these missing header files for application dev. should then be placed into the /sqllib/include library.
Or will this "over-writing" of the Server code negatively impact my installation in some way. I do not wish to jeapordize the current Linux installation that I have. (Note: I do have DB2/WIN V9.5 ESE, and Perl works perfectly.)
Thanks
wombat53

I believe I have a resolution to this problem. One of the untarred DB2 client downloads had a file - amongst many - in the untarred directory structure called "APPLICATION_DEVELOPMENT_TOOLS_9.5.0.0_linuxia32_i3 86.tar.gz". This had an include library, containing the missing files. I untarred that zip file, and copied all the header files to the instance owner's include directory, and was able to complete the PERL Manual installation on Linux (the "make" process).
I still don't know if it is required to install the run-time client and/or DSDRIVER, but this seemed to do the job.
Perhaps this will help others with the same problem.
wombat53