×
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.
We found our problem. It was not with the stored procedure definition or the java app. It was our testing tool. We use STE product from ProData to test our procedures. When we tried the procedure from a .net app it ran OK. Must be something in the way the STE product runs the procedure (I know it uses CLI level calls to run them). We are checking on the version of STE we have and are going to contact ProData if the latest version does not fix it. Thanks for the replies.
-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Thorbjoern Ravn Andersen
Sent: Wednesday, March 25, 2009 5:57 PM
To: Java Programming on and around the iSeries / AS400
Subject: Re: using java for stored procedures
Russell T. Howard skrev:
We have a couple of production Java stored procedures.
Here are some things we found while testing out:
1) The Java class must reside in the following directory:
\QIBM\UserData\OS400\SQLLib\Function
2) The class had to be a member of the default package, we were
unable to get a package specific version implemented.
Out of curiosity. Did it not work if you placed the Bar.class for
"foo.Bar" as ...\Function\foo\Bar.class ?
Classpaths are notoriously tricky :(
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.
midrange.com
