Re: SPAM-LOW: Re: Scott's JDBCR4 program from RPG

["Dave" <dave@xxxxxxxxxxxx>]

Hi Alan,

RE: #1 -- I just declare OUTPUT variables for my Stored Procedures.  I have 
not found a way to directly use a 'return value' from a Stored Procedure. 
If you can not change the Stored Procedure to add a new parameter for some 
reason, then simply create a wrapper procedure with the extra parm and use 
that to call the original Stored Procedure and set the Output parameter.

RE: #2 --  The initial link is to a forum thread I started a while back on 
calling stored procedures in general, and once I updated to the latest 
JDBCR4 I could find the "java.sql.CallableStatement" error went away for me. 
The errors are different, as Scott pointed out, but still make sure you are 
running the latest version of JDBCR4 anyhow.   From what you have posted, I 
do not think it is related.  I also do not see a reason why the last parm 
being a constant would work...  What comes immediately after this ' 
,@violationComment VARCHAR(100)' in your Stored Procedure?

Dave


--------------------------------------------------
From: "Alan Campin" <alan0307d@xxxxxxxxx>
Sent: Thursday, June 11, 2009 4:14 PM
To: "RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
Subject: SPAM-LOW:  Re: Scott's JDBCR4 program from RPG

> 1. The SQL Return statement in the SQL Stored Procedure.

> 2. Can't figure out how a trim field would be any different than a 
> constant.