by Knut Stolze <stolze@[EMAIL PROTECTED]
>
Jul 11, 2008 at 12:41 PM
esmith2112 wrote:
>> each time I saw an udf producing such a rubbish, the reason was a
>> wrong parameter list in the "create procedure" statement.
>> Unfortunately nobody protects your shared library from misinterpreting
>> the parameter list.
>
> Thanks for the tip, Udo. I thought this was a great line of thinking
> so I pursued it a little. I looked at the system catalog entries for
> the function. They're identical with one exception (on the FUNCPARMS
> table). The difference is for the CODEPAGE value. My compilation
> environment has the function's parameters set to codepage 819
> (ISO8859-1). My other database uses codepage 1252 (Windows). Could
> this be the possibility for the discrepancy? If it is, can anything
> be done about it? Can I recatalog the function with a different
> codepage?
Could you show us the source code of the function entry point of your UDF?
--
Knut Stolze
Data Warehousing for DB2 z/OS
IBM Germane Research & Development
