I realize this is an old post, but was wondering if you ever found a solution? I have a similar issue with an app that works fine when SQL Server accesses DB2 10.5 Fixpack 4, but get's this issue when accessing a "clone" of the db2 database that is running under DB2 10.5 fixpack 7. We are pretty confident that no customizations were done to the 10.5 fixpack 4 database such as to the dbm cfg or db2cli.ini to provide any special handling of alternate package collections for non-default BIND parms such as KEEPDYN. Given the connection string/datasource definitions for the connection the app uses are pretty much the same for both versions of the database aside from the host/port, we can't understand where or why KEEPDYN would even be implied for the dynamic bind related to the query being called. I have a PMR opened with IBM on it, but so far they are still researching. BTW - we are using the Microsoft DB2 OLEDB Provider not the IBM DB2 OLEDB Provider in both cases.