
Signature
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.
> On Wed, 26 Apr 2006 17:08:34 -0400, "Rhino"
> <no.offline.contact.please@nospam.com> wrote, quoted or indirectly
[quoted text clipped - 5 lines]
>
> See http://mindprod.com/jgloss/caq.html
It's interesting that you post this link because I found it before I posted.
The first thing it tells you to do for UnsatisfiedLinkError is to use
Wassup to determine the java.library.path. I did exactly that and Wassup ran
fine - but it did NOT tell me a value for java.library.path. So, to use the
vernacular, "wassup with that?".
And here's that stacktrace:
Exception in thread "main" java.lang.UnsatisfiedLinkError: set
at COM.ibm.db2.app.UDF.set(Native Method)
at com.xyz.db2v8.udf.db2general.TextUDFs.reverse(TextUDFs.java:90)
at UdfDriverV8.testReverse_DB2General(UdfDriverV8.java:102)
at UdfDriverV8.<init>(UdfDriverV8.java:26)
at UdfDriverV8.main(UdfDriverV8.java:12)
--
Rhino
Roedy Green - 27 Apr 2006 08:12 GMT
On Thu, 27 Apr 2006 00:01:55 -0400, "Rhino"
<no.offline.contact.please@nospam.com> wrote, quoted or indirectly
quoted someone who said :
>I did exactly that and Wassup ran
>fine - but it did NOT tell me a value for java.library.path. So, to use the
>vernacular, "wassup with that?".
The advice reads
"Use Wassup to determine the java.library.path system property. It is
restricted, so make sure you flip the Wassup display from safe to
restricted. Your DLL must live either on that path, or in your jar
without any package name."
Did you follow the instructions in the second sentence?

Signature
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.
Rhino - 27 Apr 2006 13:35 GMT
> On Thu, 27 Apr 2006 00:01:55 -0400, "Rhino"
> <no.offline.contact.please@nospam.com> wrote, quoted or indirectly
[quoted text clipped - 12 lines]
>
> Did you follow the instructions in the second sentence?
Yes, I ran it in both 'safe' and 'restricted' modes and neither showed me
any property called java.library.path. The same thing happened just now when
I tried it again. Lots of properties got displayed in each case, just
nothing called java.library.path. It correctly reported my Java version,
1.5.0_06 and my user name so the applet itself seems to be working fine.
--
Rhino
Roedy Green - 27 Apr 2006 08:14 GMT
On Thu, 27 Apr 2006 00:01:55 -0400, "Rhino"
<no.offline.contact.please@nospam.com> wrote, quoted or indirectly
quoted someone who said :
>COM.ibm.db2.app.UDF.set(Native Method)
that strikes me as odd. The convention is to use lower case package
names.
It should read:
com.ibm.db2.app.UDF.set
Did you use that package name anywhere in your code, particularly as a
string literal?

Signature
Canadian Mind Products, Roedy Green.
http://mindprod.com Java custom programming, consulting and coaching.
Rhino - 27 Apr 2006 13:49 GMT
> On Thu, 27 Apr 2006 00:01:55 -0400, "Rhino"
> <no.offline.contact.please@nospam.com> wrote, quoted or indirectly
[quoted text clipped - 4 lines]
> that strikes me as odd. The convention is to use lower case package
> names.
I agree that it is odd to have the 'COM' part of the package name in
uppercase but it happens to be the way IBM named that package; it's been
that way since DB2 first started supporting Java. It's not a typo, just a
name choice that doesn't comply with the standard.
> It should read:
>
> com.ibm.db2.app.UDF.set
>
> Did you use that package name anywhere in your code, particularly as a
> string literal?
The full thing, com.ibm.db2.app.UDF.set (or COM.ibm.db2.app.UDF.set)? No,
absolutely not. I have the string "UDF" in some comments and in some
System.out.println() statements of the little driver program but they all
look perfectly kosher to me.
--
Rhino