×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Robert,
SQL does not support operational descriptors.
Looking at your prototype, I don't see why you would need an operational
descriptor, here? Your fields are all fixed-sizes, and you have no
optional field. Can you explain what OPDESC is used for?
If you do need OPDESC (for calls from ILE languages.. it can't be used
from SQL) I'd suggest creating an RPG wrapper that can be invoked
without OPDESC, but calls the original procedure. Something like
D Remove_Non_AlphaNumeric_sql...
P B export
D pi 65535a varying opdesc
D inData 65535a const varying
D inCompress n const
/free
return Remove_Non_AlphaNumeric(inData: inCompress);
/end-free
P E
So this merely calls the regular routine... the advantage is that it
doesn't have an OPDESC, so it can be called from SQL. If you wanted to,
you could use overloading (by having multiple wrappers like this, each
would have a different 'external name', but the same SQL name) that pass
different sized strings or passed optional parameters, etc.
I could explain that better if I understood what the opdesc was used for.
-SK
On 9/26/2013 3:08 PM, Robert Mullis wrote:
That worked Chuck. I changed the second parm to a VARCHAR(1) and now it
finds the UDF. Now the UDF is failing with "Missing operational
descriptor." in the joblog. Apparently the OPDESC on my procedure is a
problem.
midrange.com
