The problem is neither the definition of the numeric fields as DECIMAL or
NUMERIC nor the different parameter style.
The problem is that the parameters are expected to be passed by value, but
the SQL function passes all parameters by reference (i.e. a pointer on the
data)
If you define your RPG parameters with the CONST keyword instead of the
VALUE keyword, your (SQL) function should work.
Mit freundlichen Grüßen / Best regards
Birgitta Hauser
"Shoot for the moon, even if you miss, you'll land among the stars." (Les
Brown)
"If you think education is expensive, try ignorance." (Derek Bok)
"What is worse than training your staff and losing them? Not training them
and keeping them!"
?Train people well enough so they can leave, treat them well enough so they
don't want to.? (Richard Branson)
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
dlclark@xxxxxxxxxxxxxxxx
Sent: Dienstag, 9. Januar 2018 21:33
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Subject: RE: Creating an SQL function from a service program
"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 01/09/2018
03:27:45 PM:
Bingo
THAT was it
I removed ALL the 'value' from the parameter inputs Dropped and
created the function and re-ran my test - and it worked
MUCH appreciated for all the responses
Now to make sure that everyone knows what I need to do - recompile
everything
As mentioned... It would be better to create a new small service
procedure in that service program that your SQL stored procedure could
call and then that new service procedure would call the existing
(unmodified) service procedure. That way you don't have to recompile
anything else at all.
Sincerely,
Dave Clark
midrange.com
