Thanks Adrian. We are using the PI/open flavour too. We seem to have a four argument subroutine with the first argument being the return value. I guess that this is the same thing as a three argument function?
It does seem to be working (with some warnings) and I will now do some further debugging to figure out what has changed between our older server on UV9.5 and our new one on UV10.1.18. Regards, Rob Wills (rob dot wills at tigerinfotech dot com) [EMAIL PROTECTED] wrote on 17/07/2006 02:27:27: > Here's how we do it: > > Write the code as a function with a name of "Uxxxx" (where xxxx is a > FOUR character conversion code) and the following three arguments: > > STATUS.CODE Input=the conversion code, output=the value to > set STATUS() > DATA.FIELD Input= the data to be converted > INTERNAL Input: @true = ICONV, @false= OCONV > > STATUS.CODE can be useful, as you can use conversion codes that are > longer than the specified 4 characters, you can conditionally do extra > processing based on these extra characters (eg. all the extra codes on > the end of date conversions). > > Your function should then RETURN() the required result. > > After compiling the function, you need to GLOBALLY catalog it, using > this format: > > CATALOG BP $CAC0 UCAC0 FORCE > > That's assuming the program in the BP is called UCAC0. > > Disclaimer: this all works for us in a PI/Open flavour account, I can't > see why it wouldn't work in other flavours. > > AdrianW ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
