× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Trying to connect from a linux application to IBM i. I am not the linux expert so I may be getting something translated wrong. The Linux person was looking for a DB2 ODBC driver to install and found DB2 Connect which looked like it was trying to connect but was getting rejection errors from the server. That is when I came in to look at the I security setup. After working thru a few port blocking issues on the network and telling the linux person ODBC connected on port 8471 I could see the server connect on 8471 but it still did not work. Had the linux person do some things on the linux side and along the way found that it was trying to do a DRDA connection not ODBC. Changed the port to 446 and it connected immediately and they issued the licensing error. The wording on the SQL error on the linux side makes it sound like the remote server (the i) rejected the connection due to the licensing problem. Thus making me think I needed a license on the I that I did not have.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Nathan Andelin
Sent: Wednesday, November 11, 2009 5:41 PM
To: Midrange Systems Technical Discussion
Subject: Re: DB2 on Linux to DB2/400 using DRDA

I'm not a DB2 Connect expert, but my understanding is that it provides "drivers" for "applications" to connect to remote databases (IBM i in your case, evidently). The drivers include DB2 CLI, JDBC, ODBC, ADO, ADO.Net, OLE DB, and SQL J.

If that's the case, then I'm confused about your reference to DB2 for Linux. DB2 Connect would make more sense if you were attempting to connect from a Linux "application" to an IBM i database, and needed an ODBC driver.

Are you trying to connect to a Linux database from an IBM i application? What am I missing?

-Nathan.



----- Original Message ----
From: Mike Cunningham <mike.cunningham@xxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Sent: Wed, November 11, 2009 2:44:06 PM
Subject: RE: DB2 on Linux to DB2/400 using DRDA

Do you know if that is a license purchased for the linux server side or on the iSeries side? So we own DB2/400 and can use it all we want including for remote ODBC and JDBC connections and we can get DB2 for Linux for free, but if we want to use DRDA to connect the two it might be a $12K license? If that turns out to be true (will check with our BP) I think we will drop the DRDA option and go ODBC. I did see DB2 Connect Personal Edition for Linux for $515. Maybe that will suffice since we are only talking one sever needing to connect.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Lukas Beeler
Sent: Wednesday, November 11, 2009 3:41 PM
To: Midrange Systems Technical Discussion
Subject: Re: DB2 on Linux to DB2/400 using DRDA

On Wed, Nov 11, 2009 at 21:36, Mike Cunningham <mike.cunningham@xxxxxxx> wrote:
We have a linux server running DB2 (got it free from IBM). We want to connect that linux install of DB2 to DB2/400. We have it setup to do this (it uses DRDA) and the connecting is being made but we get a licensing error that we do not have a valid DB2 Connect license (see link) Any idea what we have to do to get licensed for this? Would this be a license on the DB2/400 side or on the DB2 for Linux side?

You need a DB2 Connect license (duh). It's very expensive. We had a
quote for 30 users here, and the price was about 12k or something
around that.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.