Re: JTOpen jdbc driver question about calling stored procedures.

Thank you for your time. The link was helpful, but I do understand the
differences.


The thing I don't understand is with IBM's note about getting the
descriptor index not valid error message.

For the location of the procedure, make sure the schema name is used, not
the library name.

What exactly are they referring too? Are they referring to line of code
that is calling the procedure? Even if I'm using system naming and library
list. Should the call look like this...

DECLARE @VALUE CHAR(80);
SET @VALUE = '';
CALL ODWPROD.GetNextWorkingOrder(@VALUE);


instead of

CALL GetNextWorkingOrder(@VALUE);


Or are they talking about the EXTERNAL NAME on the create procedure?

CREATE PROCEDURE ODWPROD/GETNXTWRKORD (
INOUT NXTWO CHAR(80) )
LANGUAGE CL
SPECIFIC ODWPROD/GETNXTWRKORD
NOT DETERMINISTIC
NO SQL
CALLED ON NULL INPUT
EXTERNAL NAME EBI001C <---- ***********
PARAMETER STYLE GENERAL ;

This is how I would prefer it to be, but the vendor is saying that it must
be
CREATE PROCEDURE ODWPROD/GETNXTWRKORD (
INOUT NXTWO CHAR(80) )
LANGUAGE CL
SPECIFIC ODWPROD/GETNXTWRKORD
NOT DETERMINISTIC
NO SQL
CALLED ON NULL INPUT
EXTERNAL NAME 'ODWPROD/EBI001C' <---- ***********
PARAMETER STYLE GENERAL ;

When creating it. I don't want it to be hard coded. ALDON doesn't allow
it to be hard coded when promoting when using PSEUDO source. You would
have to create outside of Aldon, the bring it in with NO SOURCE, then
promote it up.

But that defeats the purpose of letting the system find unqualified objects
based on the library list.

That being said, I don't see how I can specify the SET PATH on this
particular CREATE PROCEDURE statement.



On Wed, Dec 12, 2012 at 10:15 PM, Michael Schutte <mschutte369@xxxxxxxxx>wrote:

Yes it works from I series nav

Sent from my iPhone

On Dec 12, 2012, at 9:33 PM, Sam_L <lennon_s_j@xxxxxxxxxxx> wrote:

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

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.