> Hi, I'm not sure, whether this is the right place for my question. If not,
> please point me to the correct group.
[quoted text clipped - 5 lines]
> Windows? It is neither part of my DB2 installation nor of the (MS) Visual
> C++.
> SQLPREP - shows an old vintage of DB2 - perhaps Version 2.x...(Circa
> 1995.. you will have more problems with porting code
> 11 years old).
I don't know. I am the new one in this company.
> You need to Install Application Development client on Windows machine
> and establish connectivity to z/OS host (MVS is long
MVS still running on host maschine (/370 maybe old, too)
> gone too). Either use DB2 Connect Server somewhere on the network - or
> use DB2 Connect Personal Edition on you Windows
> XP machine.
Thanks,I will see whether I can get it somewhere.
> Somehow I think you will post your questions very frequently from now
> on - unless you recode the application in Java
Sorry, there's no chance. Management dictates the rules :-((
> (Java code with DB2 UDB Universal JCC Driver Type 4 - only needs Java
> runtime; DB2 Connect license file and connectivity
> to z/OS).
As mentioned above - there is no chance (the new employee has to do what the
big boss say, and keep his mouth shut).
> PS: SQLPREP is replaced in DB2 world by command: db2 prep ...
Thanks for this hint, I tried it.
But - now I have another problem, maybe one can help me, too:
I tried a little example:
EXEC SQL INCLUDE SQLCA
EXEC SQL BEGIN DECLARE SECTION;
char ATTR1[2];
char ATTR2[2];
EXEC SQL END DECLARE SECTION;
EXEC SQL SELECT ATTR1 INTO :ATTR1 FROM TXA.TBL WHERE ATTR2 = :ATTR2;
and I get a message
SQL30073 "0x2112" Parametervalue "0x0000" not supported.
I did not find the meaning of this message (with value "0x2112") anywhere
(GOOGLE was not friendly to me).
If I enter the select directly I get the correct result.
> Best regards,
>
> Jan M. Nelken
Thanks.
Best regards back,
Klaus
Gert van der Kooij - 19 Mar 2006 02:32 GMT
> Thanks for this hint, I tried it.
>
[quoted text clipped - 28 lines]
> Best regards back,
> Klaus
I've found a description about this error message in the redbook at
http://www.redbooks.ibm.com/redbooks/pdfs/sg246435.pdf
that this message might be changed into a more describing message when
using at least FP5. Maybe updating to the latest fixpack level might
help you also to get a more meaningfull message.