Hi Dave
Just to let you know that when I saw how much needed to be re-compiled and then tested - to prove that the change still worked
Well - let me just say
The engineer/scientist inside of me wanted to make these changes so that everything will work correctly
But the lazy S.O.B. inside of me started shouting - AND ALL THAT TESTING TO DO!!!!!
I ended up doing what you suggested
Made a separate service program that called the original service program
I just tested my new service program - and it works perfectly
Now let me create the function from that new service program and see the results
Alan Shore
E-mail : ASHORE@xxxxxxxx
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of dlclark@xxxxxxxxxxxxxxxx
Sent: Tuesday, January 09, 2018 3:33 PM
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
