Synametrics Technologies

I am having trouble connecting to DB2 via WinSQL, but only when executing in batch mode, via a *.wet file.

Current Set-up:  WinSQL Professional v 10.0.154.694, running on Windows 7 Enterprise, 64-bit

When running the WinSQL 64-bit client, the error message is: 08-Aug-2016 18:14:07 [ERROR] {} - Unable to find license file for WinSQL drivers.

When running the WinSQL 32-bit client the error message is: 08-Aug-2016 18:14:07 [ERROR] {} - Unable to find license file for WinSQL drivers.

I would prefer to use the 64-bit version if possible.  But for now I only want to get through my month-end any way I can.

After reading through the WinSQLKB, I have suspicions about the setting of Drivername within:

C:\Users\\AppData\Roaming\WinSQL\cache\DB2.info and C:\Users\\AppData\Roaming\WinSQL\cache\DB2\AIX64.info

Both of those files contain the following parameter setting: DB2CLI.DLL

According to your knowledge base, the driver parameter should be set to DB2CLIO.DLL when running in 64-bit mode.

I believe my ODBC manager configurations are correct, given that I can run my queries interactively.  I also verified the driver references in both ODBC Managers

To access my 32-bit ODBC manager, I run: C:\Windows\SysWOW64\odbcad32.exe. Drivers in 32-bit mode correctly reference DB2CLI.DLL

To access my 64-bit ODBC manager, I run: C:\Windows\System32\odbcad32.exe. Drivers in 64-bit mode correctly reference DB2CLIO.DLL

I just need some help tweaking my system to recognize the same drivers in batch mode that I am using interactively.

Please advise.

Dear Dennis,

Which ODBC driver are you using to connect to your DB2 backend? Is it the driver that comes with WinSQL32 or it is the driver from IBM. I see references to DB2CLI.DLL and therefore, assume it is the IBM's driver. In that case, the error you see in the log is irrelevent.

What do you see in the log AFTER this error?

Initially I registered and used the ODBC drivers built within WinSQL.  When the error message appeared, I then deregistered the WinSQL DB2 driver, to see if the IBM versions did the trick.  But they failed as well, both in the 32-bit and 64-bit attempts.

The error message I get is:

Export Status - Expected 0 records in 00:00:32.5532550, with 0 error(s).

In all cases the feedback was within 30 seconds or so.

But your response has given me an idea.  Could it be that I need to re-register the WinSQL DB2 ODBC driver, then create unique WinSQL-specific connections, Utilizing those drivers, not the IBM ones?  If so, I will need some assistance in completing that task.  My DBA gave me the following instructions for ODBC setup:

db2 catalog tcpip node <myAlias> remote <MyServerAddress> server <MyPort>
db2 catalog db <myAlias> as <myAlias> at node <MyNode>
db2 catalog user odbc data source <myAlias>

Those commands have always worked for me when I used WinSQL v9 or prior.

Or perhaps I am on the wrong track altogether. Please advise. 

Dennis,

Are you able to run this export manually - meaning loading the *.wet file in the Export Template Wizard?

Can you please call our support department. It is a bit difficult to solve this without further investigation. Our phone number is 609-750-0007

Imran