RE: DB2 Connect vs. JTOpen jdbc driver

Mark,

You identified my frustration with:
"... it appears that IBM doesn't really want anyone using DB2 for i as an enterprise database..."

I think I remember something about making the iSeries (or whatever name at the time) the
"db server of choice" - which I thought was a great idea...

Thanks again!

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Murphy/STAR BASE Consulting Inc.
Sent: Thursday, July 05, 2012 10:33 AM
To: Midrange Systems Technical Discussion
Subject: RE: DB2 Connect vs. JTOpen jdbc driver

Sorry for the late reply, but I did want to clarify. DB2 Connect personal edition is simply a DRDA client for windows. It lets you connect to DRDA databases (specifically DB2 for i) from a windows client. I have looked at the pricing for this product, and it appears that IBM doesn't really want anyone using DB2 for i as an enterprise database since they have made the Windows client prohibitively expensive.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx

-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Gary Thompson
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Date: 06/26/2012 11:10AM
Subject: RE: DB2 Connect vs. JTOpen jdbc driver

Mark,
I am not understanding your point, I guess mainly the "native client" part.

As far as I know "the native client" on i does not directly support queries against non-DB2 remote DB.

We looked at DB2 connect and the price IBM quoted seemed high, and it appeared to have more function than our project or future needs require, so we could not justify the expense.
 
True, we did install a full blown DB, but that is part of the 3rd party pick system we are installing, so this was not a deciding factor for us.

We did look at Scott Klement's service program and open source ArdGate (which has a lot to recommend it) and are now using another 3rd party product and are pleased with our results.


 

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Mark Murphy/STAR BASE Consulting Inc.
Sent: Tuesday, June 26, 2012 8:35 AM
To: Midrange Systems Technical Discussion
Subject: RE: DB2 Connect vs. JTOpen jdbc driver

So using the native client is overkill but installing a full blown database isn't?  Interesting.

Mark Murphy
STAR BASE Consulting, Inc.
mmurphy@xxxxxxxxxxxxxxx

-----midrange-l-bounces@xxxxxxxxxxxx wrote: -----
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
From: Gary Thompson
Sent by: midrange-l-bounces@xxxxxxxxxxxx
Date: 06/25/2012 01:49PM
Subject: RE: DB2 Connect vs. JTOpen jdbc driver

My 2 cents is DB2 connect is overkill unless you have a large enterprise needing to connect to a mix of databases on a mix of servers with DB2 being the main enterprise db.

I have found going to/from MS Sql to DB2 relatively easy.  One of my first projects used Access pass-through queries with an MS Sql Server back end that had an iSeries DB2 database connection.

After that, we did some .net based connections using C#.

All that is some years past, but, aside from licensing MS Sql server and .net developer tools, we had a relatively small budget.


 
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Dean Eshleman
Sent: Monday, June 25, 2012 11:25 AM
To: 'midrange-l@xxxxxxxxxxxx'
Subject: DB2 Connect vs. JTOpen jdbc driver

We purchased a Windows application that needs to connect to our System I box to retrieve data.  The vendor thinks they need to use DB2 Connect to do that.  I was wondering why they couldn't just use the JDBC driver that is available via the JTOpen toolbox.  Could someone explain why you would need DB2 Connect?

Dean Eshleman
Software Development Architect

Everence Financial
1110 North Main Street
PO Box 483
Goshen, IN 46527
Phone: (574) 533-9515 x3528
www.everence.com<http://www.everence.com>






________________________________________
Confidentiality Notice: This information is intended only for the individual or entity named. If you are not the intended recipient, do not use or disclose this information. If you received this e-mail in error, please delete or otherwise destroy it and contact us at (800) 348-7468 so we can take steps to avoid such transmission errors in the future. Thank you.
_______________

--