× 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.


  1.  Home
  2. MIDRANGE-L
  3. December 2012

Re: JTOpen jdbc driver question about calling stored procedures.

Can you call the procedure from iSeries Nav? That might help figure out where the problem lies.

Also look at SET CURRENT PATH and SET CURRENT SCHEMA in the SQL reference manual and see what they say about unqualified references.

You might want to take a look at this article which tries to explain some of the nuances of *SYS vs *SQL naming:

http://www.mcpressonline.com/tips-&-techniques/database/techtip-do-you-understand-the-db2-for-i-environment-settings.html

Sam

On 12/12/2012 9:09 PM, Michael Schutte wrote:
Yes he is calling the stored proc. which is calling the cl program. It's an external SQL procedure.

He is getting the message describe in the previous email when the external name on the create procedure is not hard coded to the library it's in. When it's hard coded it works.

I don't want it hard coded is there a solution? Or is what I found on IBM site true.

The procedure is getnextworkingorder. This is suppose to call cl ebi001c

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.