We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Looking for ability to specify Data Server Driver and Nuget package for different appls on same .NET server
We are interested in IBM providing the ability to support an application using a Db2 NuGet package for Db2 connectivity and another application using DS Driver or Db2 Client on the same .NET server for compatibility between the Db2 NuGet package for Azure Cloud and the Db2 Client software. We have an application which is deployed in the MS Azure Cloud environment and uses a Db2 NuGet package included with the application for connectivity to z/OS Db2. When the application was deployed on a ‘Utility’ .NET server where a Db2 Client was installed for a different application, the application no longer resolved the Db2 connectivity with the NuGet package but looked for the Data Source to be resolved by the Db2 Client software.
It was suggested that we add this parameter to the application:
That was done and the application worked without its Data Source being cataloged in the Db2 Client. There was an entry in the Db2 Client db/node directory for another application but not this application.
We then went to deploy the application on a second .NET server and it failed with these messages:
ERROR  [IBM] SQL0843N The server name does not specify an existing connection. SQLSTATE=08003
ERROR  [IBM] CLI0119E Unexpected system failure. SQLSTATE=58004
I checked the second server and found it did have the Db2 Client installed but there was no entry in the db/node directory on this server. I added the entry to match the first server and the application worked. The entry I added was not the entry this application needed so I know it began using the NuGet package but for some reason, we needed at least one data source cataloged in the Db2 Client for that to work.
We would like a supported solution which allows the application running on MS Azure Cloud platform to deploy on a .NET server for utility purposes such as submitting jobs through Autosys and continue to use the Db2 NuGet package. Today if the targeted .NET server has another application using the Db2 Client for connectivity, even with a suggested workaround (DB2DSDRIVER_CFG_PATH), we had mixed results depending on whether or not the Db2 Client on the .NET server had a db/node directory entry. We are looking for a means of specifying with the application using the Db2 NuGet package, that the NuGet package should always be used to resolve Db2 Connectivity, regardless of the presence of a Db2 Client or DS Driver Package on the hosting .NET server. This would allow the application using the NuGet package on the MS Azure Cloud platform to run in multiple .NET environments and not rely on Db2 Client/DS Driver configurations in those environments.
I opened Case TS003513738 previously when we encountered the issue after deploying the application on the .NET Utility server. This Case may provide additional details as we worked with the IBM Support team.
Do not place IBM confidential, company confidential, or personal information into any field.