Joe, I use *LANGIDSHR when I need both, case insensitivity and an
ASCII-like collating sequence (numbers before letters). Also, it allows
(AFAIK) for the correct collating sequence, regardless of the code base
used. For instance, in Spanish we have a letter that is just like a 'N'
with a tilde on top (Ñ). If I use, for instance, *HEX, the lower case
version (ñ) comes AFTER the upper case version (Ñ), because the upper case
letter corresponds (IIRC) to the # character in EBCDIC (appears before
'A'). *LANGIDSHR solves this.
The downsize is that, at least in V5R3, it seems to me that SQL tends to
use CQE instead of SQE when defining a table with *LANGIDSHR...
IBM Certified Systems Expert — eServer i5 iSeries
This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact