Hello,
We are dealing with double byte characters throughout our application and it has came to our attention that there appears to be a discrepancy between vvIN_utf16 and the utility function it calls vvUtility_decodeUTF16. If you look at the interface definitions below you will see that the maximum alpha field size vvIn_utf16 can pass is 50, I am assuming this is an oversight.
We are currently invoking vvUtility_decodeUTF16 directly has we have fields larger than 50a.
Is there any chance we can have a fix please ?
Thanks
We are dealing with double byte characters throughout our application and it has came to our attention that there appears to be a discrepancy between vvIN_utf16 and the utility function it calls vvUtility_decodeUTF16. If you look at the interface definitions below you will see that the maximum alpha field size vvIn_utf16 can pass is 50, I am assuming this is an oversight.
Code:
p vvIn_utf16 b export d pi 16383c d inField 50a const varying options(*varsize)
Code:
p vvUtility_decodeUTF16... p b export d pi 16383c d inHex 65532a const varying options(*varsize)
Is there any chance we can have a fix please ?
Thanks
Comment