I could be wrong since I've never used NLS on U2, but I think that somewhere there is a table identifying upper/lowercase pairs.
In the default locale, char(253) is the value mark and doesn't have an associated case pairing, but in some other locales it is "latin small letter y with acute" and pairs with char(221). So a string created on on a system with one local could upcase differently if moved to a system with a different local. However, I think there's also a setting for what characters are used as system delimiters. So if char(253) is needed as a data character then @VM would be redefined to be something different (I hope :)) So assuming that the same locale was always used, OCONV, OCONVS, AND UPCASE/DOWNCASE should always case the same way. On Jun 23, 2011, at 8:42 PM, Richard Lewis wrote: > I understand matrix operations well enough to use them frequently, and > in light of this discussion, the following question popped into my > mind: > > Is there any difference between: > > X = OCONV(X,'MCU') > > and: > > X = OCONVS(X,'MCU') > > Has anyone experienced the results being different? > > Thanks! > > Richard Lewis > > > On Wed, Jun 22, 2011 at 9:08 AM, George Gallen <[email protected]> > wrote: >> UPCASE() will also function as OCONVS() >> >> If you put in a dynamic array into UPCASE(), it will upcase the entire >> string and >> leave the @VM, @AM... untouched. >> >> I use this on UV when reading items, especially for searching, I'll upcase >> the entire >> dynamic array, then proceed to do my indexes or locates. >> >>> -----Original Message----- >>> From: [email protected] [mailto:u2-users- >>> [email protected]] On Behalf Of Martin Phillips >>> Sent: Wednesday, June 22, 2011 6:32 AM >>> To: U2 Users List >>> Subject: Re: [U2] uppercase >>> >>> Hi Jeff, >>> >>> The difference is probably only one of performance. Using OCONV >>> requires the >>> conversion code to be decoded in order to work out what to do. Using >>> UPCASE() can go straight off to do the real work without any additional >>> decoding. >>> >>> I suspect not, but there may be some difference of interpretation if >>> you >>> have NLS installed. >>> >>> >>> Martin Phillips >>> Ladybridge Systems Ltd >>> 17b Coldstream Lane, Hardingstone, Northampton NN4 6DB, England >>> +44 (0)1604-709200 >>> >>> ----- Original Message ----- >>> From: "Jeff Butera" <[email protected]> >>> To: <[email protected]> >>> Sent: Wednesday, June 22, 2011 11:24 AM >>> Subject: [U2] uppercase >>> >>> >>>> On unidata, can anyone shed light on the differences between >>> UPCASE(...) >>>> and OCONV(...,'MCU')? >>>> >>>> I know OCONVS(...,'MCU') will preserve @VM and other unidata >>> delimiters, >>>> but for single valued data is their any difference in the above? >>>> >>>> >>>> -- >>>> Jeff Butera, PhD >>>> Manager of ERP Systems >>>> Hampshire College >>>> 413-559-5556 >>>> >>>> _______________________________________________ >>>> U2-Users mailing list >>>> [email protected] >>>> http://listserver.u2ug.org/mailman/listinfo/u2-users >>> >>> _______________________________________________ >>> U2-Users mailing list >>> [email protected] >>> http://listserver.u2ug.org/mailman/listinfo/u2-users >> _______________________________________________ >> U2-Users mailing list >> [email protected] >> http://listserver.u2ug.org/mailman/listinfo/u2-users >> > _______________________________________________ > U2-Users mailing list > [email protected] > http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
