× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




I am trying to write a Java stored procedure and am coming across what seems like a classpath issue but am not sure how to solve it.

I wrote a class (ccps.Silk) and created a "main" method for testing.
When I run the java class from qshell the results are as expecting, performing exactly as it should.
When I register the method as a stored procedure I am getting the errors below.
The part that stands out to me is the "No suitable driver" statement.
The driver exists in the db2_classes.jar file that is symbolically linked in the /QIBM/ProdData/Java400/ext and /QIBM/UserData/Java400/ext directories.

Why does it appear the driver cannot be found when calling the stored procedure, but works fine when running the Java class directly?


Message . . . . : External function exception - SQLSTATE 08001, SQLCODE 0.
Cause . . . . . : An external function exception occurred on the application
server. Either the SQLSTATE and SQLCODE are not recognized by SQL or the GET
DIAGNOSTICS DB2_TOKEN_STRING is not valid for the corresponding SQL message.
The GET DIAGNOSTICS MESSAGE_TEXT is .
The GET DIAGNOSTICS DB2_TOKEN_COUNT is .
The GET DIAGNOSTICS DB2_TOKEN_STRING is No suitable driver.
The relational database is *N and the product identification is QSQSTPJC.
Recovery . . . : Refer to the product specific documentation for the
application server.


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.