DB2 Connect on the IBM i is a licensed product. It speaks DRDA directly
to the database. We looked at it a few years ago when we first started
exploring application modernization so that could integrate our product
that runs strictly on linux with our updated IBM i product. Because of
the cost we ended up not integrating the products and instead have
written everything in PHP running directly on the IBM i since that
didn't need the DB2 connect license. It's a vague memory, but I remember
having a trial license for 30 days, and the DB2 Connect was about 3-4
times faster than the odbc driver that IBM provides in client access,
and about 5 times faster than the jdbc driver in JTOPEN.
Kevin Bucknum
Senior Programmer Analyst
MEDDATA/MEDTRON
Tel: 985-893-2550
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Dearing
Sent: Tuesday, November 10, 2015 8:02 AM
To: Midrange Systems Technical Discussion
Subject: Can someone give me a non-marketing explanation of DB2 Connect?
Ok so first a story, because maybe that's the wrong question. IBMs
website makes DB2/connect sounds like an ODBC or JDBC driver. That's not
entirely true from what I can surmise.
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?
Justin
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
midrange.com
