I can imagine most of the .NET APIs currently connecting to DB2 are using Entity framework with your EF DB2 drivers (EntityFramework.IBM.DB2).
With the release of .NET Core 3.0 & Entity Framework 6.3, the EF 6.3 runtime package now targets .NET Standard 2.1 which means that Entity Framework is now cross platform. More info here.
To be able to use the Entity Framework 6.3 on .Net Core runtime, IBM drivers (EntityFramework.IBM.DB2 package) needs to be ported to .NET Core too.
Why is it useful?
|Who would benefit from this IDEA?||the whole .NET community who has to connect to DB2|
How should it work?
We would really appreciate if you could support the products you've developed and add EF6.3 support to your DB2 drivers (EntityFramework.IBM.DB2 package).
Any API using your DB2 drivers would be deploy-able to cloud - large corporations including ours have introduced "cloud-first" policy.
All of APIs will have to migrated to EF Core - this is very time consuming and all of your clients will have to undergo this process.
Consider being more transparent and share a plan on what you are supporting and what not (ideally with timeline included). To be able get any answer from you, we had to chase you through many various channels and this does not make us very happy to use your products going forward. By the way, we still do not have an answer with your plan. The original question is also still unanswered:
NOTICE TO EU RESIDENTS: per EU Data Protection Policy, if you wish to remove your personal information from the IBM ideas portal, please login to the ideas portal using your previously registered information then change your email to "email@example.com" and first name to "anonymous" and last name to "anonymous". This will ensure that IBM will not send any emails to you about all idea submissions