1. Several existing N/E programs use an existing Network ODBC connection with Library 'X' specified for the sqlpkg library (connecting from the Network to an AS400).
2. We changed the Network ODBC connection sqlpkg library value from Library 'X' to Library 'Y'. We deleted all sqlpkgs from the AS400 Library 'X'.
3. The existing N/E executables were executed from the Network. AS400 sqlpkgs are still being created in Library 'X' (instead of Library 'Y'). However, Library 'Y' is specified in the Network ODBC configuration.
4. New N/E executables (brand new source names) are being created in the correct AS400 package Library 'Y'.
Does anyone know why the old SQLPKG library name 'X' is being retained on the existing code - even when the .EXE file is re-created using the new ODBC definition specifying SQLPKG Library 'Y'? Any assistance would be GREATLY appreciated!
It would probably be best to ask this question of IBM as SQLPKG is their technology and is not from Micro Focus.
Micro Focus Development has asked the following questions:
What version of Net Express are you using?
How are you creating your applications, .EXE, .DLL, .INT, .GNT?
Which ODBC driver are you using?
Are you using OpenESQL throughout?
What SQL compiler directives are you using?
Did you clean and rebuild your existing applications after changing the network configuration?
Maybe the ODBC driver is caching stuff locally and you have to rebuild the application to purge it.
This is just a wild guess.though as we really have no experience with the SQLPKG support from IBM.
Thanks.
1. Several existing N/E programs use an existing Network ODBC connection with Library 'X' specified for the sqlpkg library (connecting from the Network to an AS400).
2. We changed the Network ODBC connection sqlpkg library value from Library 'X' to Library 'Y'. We deleted all sqlpkgs from the AS400 Library 'X'.
3. The existing N/E executables were executed from the Network. AS400 sqlpkgs are still being created in Library 'X' (instead of Library 'Y'). However, Library 'Y' is specified in the Network ODBC configuration.
4. New N/E executables (brand new source names) are being created in the correct AS400 package Library 'Y'.
Does anyone know why the old SQLPKG library name 'X' is being retained on the existing code - even when the .EXE file is re-created using the new ODBC definition specifying SQLPKG Library 'Y'? Any assistance would be GREATLY appreciated!
One of the avenues we tried was deleting the ODBC definition and re-creating it with the new SQLPKG library name -- and that worked! (Still don't understand why a new ODBC definition worked but changing the existing one didn't...but oh well!)
Thank you for the advice -- we might need more assistance sometime in the future.
1. Several existing N/E programs use an existing Network ODBC connection with Library 'X' specified for the sqlpkg library (connecting from the Network to an AS400).
2. We changed the Network ODBC connection sqlpkg library value from Library 'X' to Library 'Y'. We deleted all sqlpkgs from the AS400 Library 'X'.
3. The existing N/E executables were executed from the Network. AS400 sqlpkgs are still being created in Library 'X' (instead of Library 'Y'). However, Library 'Y' is specified in the Network ODBC configuration.
4. New N/E executables (brand new source names) are being created in the correct AS400 package Library 'Y'.
Does anyone know why the old SQLPKG library name 'X' is being retained on the existing code - even when the .EXE file is re-created using the new ODBC definition specifying SQLPKG Library 'Y'? Any assistance would be GREATLY appreciated!
One of the avenues we tried was deleting the ODBC definition and re-creating it with the new SQLPKG library name -- and that worked! (Still don't understand why a new ODBC definition worked but changing the existing one didn't...but oh well!)
Thank you for the advice -- we might need more assistance sometime in the future.
