db2 v9 license issue

[Sergey Kashyrin]

Hello,

I have a small C++ program which connects to different DB2 instances
including local DB2 ESE v9.1 on WinXP x64 (AMD64 version of DB2) and remote
z/OS DB2 v7 using the same "db2api.lib" from v9.2.

64-bit version of the program works perfectly (linked with 64-bit library
\db2\lib\db2api.lib).

32-bit version (linked with 32-bit library \db2\lib\win32\db2api.lib) does
not want to connect to remote z/OS DB2 giving
sqlcode = -8002, sqlstate=42968

Any reasons to work in 64-bit and not to work in 32-bit ???
Different license managers / registry entries ? Need some additional
licenses ?
Any ideas ?

Regards,
Sergey

[Darin McBride]

Sergey Kashyrin wrote:

Hello,

I have a small C++ program which connects to different DB2 instances
including local DB2 ESE v9.1 on WinXP x64 (AMD64 version of DB2) and
remote z/OS DB2 v7 using the same "db2api.lib" from v9.2.

64-bit version of the program works perfectly (linked with 64-bit library
\db2\lib\db2api.lib).

32-bit version (linked with 32-bit library \db2\lib\win32\db2api.lib) does
not want to connect to remote z/OS DB2 giving
sqlcode = -8002, sqlstate=42968

Any reasons to work in 64-bit and not to work in 32-bit ???
Different license managers / registry entries ? Need some additional
licenses ?
Any ideas ?

This looks vaguely familiar. I think v8 FP14 will fix it as far as v8.2 is
concerned, and it seems like it should be in FP2 for v9.1 (found too late
for FP1 which is due out Real Soon Now(TM)). You should open a PMR with
IBM to confirm my suspicions, and, if I'm right, I think they'll give you
APAR numbers, and a firmer commitment about when the fix will be available.
And, if I'm wrong, well, then they'll help drill down to the real
problem ;-)

Have you tried running your 32-bit version on a 32-bit WinXP with the 32-bit
version of DB2? (Perhaps in a VMWare session or something?) If my
suspicions are correct, this should work fine.