On 11/10/2015 9:01 AM, Justin Dearing wrote:

I installed DB2 Express-C on my windows laptop. I can talk to it with
SQLWorkbenchJ the same as my clients IBM i's (but with a different JDBC
jar. Everything is hunky dory. The install created an ODBC driver for me.

In PHP I used db2_connect() to talk to the windows local db2 instance from
windows with a connection string
"DATABASE=sample;HOSTNAME=localhost;UID=zippy;PWD=****". It worked. Process
monitor confirmed it was actually making a TCP connection, not named pipes
and not some shared memory connection like Microsoft SQL Server allows for
localhost connections. However, if I set the hostname to that of an IBM i
that I can connect via SQLWorkbench with jtopen, it doesn't even try to
make the TCP connection. I just get the following error:

Error connecting to DB2. 08001 [IBM][CLI Driver] CLI0199E Invalid
connection string attribute. SQLSTATE=08001 SQLCODE=-99999

So, is the ODBC driver not letting me connect because its checking some
license entitlement?

There isn't one, single DB2. There are three of them:
DB2 for z (mainframe)
DB2 for LUW (Linux, Unix, Windows)
DB2 for i (that's us!)

Each one needs a different ODBC driver. The ODBC driver for DB2 for i
comes with IBM Access for Windows, and there's an equivalent in the
Access Client Solutions package as well. And so: What's your entire
connexion string? Are you using the DB2 LUW driver to try to talk to
IBM i? That might work, but DB2 for i has a different port. 446 if
memory serves.

You can install Access for Windows 'selectively' - only installing the
ODBC drivers if you prefer.

I tried installing PHP on my PC to try it out but ran into the typical
cascade of failures trying to wedge PHP into my existing Apache 2.2
install. I'm not looking for support for that; just want to let you
know that I couldn't test anything. Sorry.


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].