thanks for your infos. Again, please realize that I have no access
to DB2 whatsoever, unfortunately, so I depend on information and
researching the Internet.
A few remarks:
It seems that this is not a BSF4ooRexx problem per se (mapping and
picking the correct methods looks correct), but one using JDBC with
DB2. Maybe you could write a small Java program matching the Rexx
logic 1:1, just for testing purposes?
- boxing is not necessary in your case as the method implies
that a string is used as an argument (setJccStringAtName(...)),
- explanation: boxing is only necessary if a method has more
than one signature involving primitive types (boolean, byte,
char, short, int, long, float, double) and the method picked
by default by BSF4ooRexx is the wrong one (e.g. there is a
method that expects a string as an argument, but there are
also methods expecting primitives, e.g. a string with a value
of "0"; in such a situation boxing determines exactly which
method should be picked)
- Researching DB2 with "ERRORCODE=-4461, SQLSTATE=42815" brings
not sure that relates to your problem; but there is also e.g.
here is the search url for these hits:
- the errortext from the Java exception includes a German
message text that indicates that the bind variable called "name"
cannot be found; are you sure that preparing has worked (e.g. is
there a return value that indicates success/failure) ?
- one more question: what character encoding are the strings
using in DB2 in your case?
Not sure, how this helps you, keeping my fingers crossed!