Problem with an SQL UDF created from a procedure within a service program

Before I forget, we are on V7r3
I have a procedure (NEXTNUMBER) within a service program (VALUES)
This is working in a number of programs
I even created a test program that uses this procedure, just so that I could STRDBG and look at the logic flow
It works
It accepts 2 parameters, the second one being optional
First parameter is a char(50) parameter
Second parameter is a logical parameter

Below is how I created the SQL function
When I run the function in STRSQL

select NBTYGPL.NEXTNUMBER('ALAN SHORE TEST')
from SYSIBM.SYSDUMMY1

Using STRDBG in another session (after using STRSRVJOB), I can see that the first parameter is garbage
Anyone any idea what I did wrong?

As always - all answers gratefully accepted

Here is how I created the SQL function

CREATE FUNCTION NBTYGPL.NEXTNUMBER (
INORD CHAR(50) )
RETURNS NUMERIC(12, 0)
LANGUAGE RPGLE
SPECIFIC NBTYGPL.NEXTNUMBER
NOT DETERMINISTIC
NO SQL
CALLED ON NULL INPUT
DISALLOW PARALLEL
EXTERNAL NAME 'NBTYGPL/VALUE(NEXTNUMBER)'
PARAMETER STYLE GENERAL



Alan Shore
E-mail : ASHORE@xxxxxxxx<mailto:ASHORE@xxxxxxxx>
Phone [O] : (631) 200-5019
Phone [C] : (631) 880-8640
'If you're going through hell, keep going.'
Winston Churchill