×
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.
I would be curious as to the why's to selecting DB2 connect. Unless maybe they built their .Net core stuff before the ODBC drivers were available in the .Net core platform.
Maybe they needed heterogeneous databases joins across multiple db2 platforms.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
------------------------------
message: 2
date: Thu, 24 Jun 2021 17:22:37 -0400
from: John Yeung <gallium.arsenide@xxxxxxxxx>
subject: Re: Connect to IBMi DB2 using an OLE DB connection
On Thu, Jun 24, 2021 at 3:05 PM Matt Olson via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
The .NET Core drivers are actually very nice, it's a simple nuget package you install in your application and nothing else is needed. The only thing needed if interacting with DB2 on the IBMi is to push the DB2 Connect server license key to the IBMi and that's it.
How "nice" the drivers are was never an issue. The issue is that connecting to IBM i using that method requires Db2 Connect. (In other words, requires a lot of money. If you don't already have Db2 Connect, the likelihood is that you aren't going to anytime soon.)
The ODBC driver for IBM i is free. And it works well enough for most people, including Richard Schoen, who is probably the biggest .NET proponent I know of among IBM midrangers.
John Y.
midrange.com
