From: Harald O. <har...@el...> - 2025-04-25 09:57:34
|
Am 25.04.2025 um 11:46 schrieb Jan Nijtmans: > Op vr 25 apr 2025 om 09:47 schreef Harald Oehlmann: >> Dear Jan, >> thanks for the action. I will test later or next week. >> The example given by Ashok was a driver to the IBM data base which was >> loaded as a dll into TCL. This 3rd party driver did not work any more >> due to the manifest change. > > My guess is that the API used by this IBM DLL is expecting > cp1252, but Tcl is providing/retrieving utf-8-encoded data > for it. Do you know where the Tcl wrapper-code for this > IBM dll is? I think there's nothing wrong with the IBM dll, > It's just that Tcl should respect the IBM API. > > Is the code here? > https://github.com/memmertoIBM/db2tcl/ > > Regards, > Jan Nijtmans To my knowledge, the dll does not work any more internally, as the interface DLL to the DB depends on it. The issue is not related to TCL expect that the manifest value makes it not working any more. To my knowledge, the concerned user case has no direct TCL interface in the sense, that data from TCL is transfered to the data base and vice versa. That is why it took so long to find the issue. Harald |