Okay, bear with me, I'm old and slow <grin>.

What are the steps? Do you set the SQL session parameter to LANGIDSHR in STRSQL and then run the CREATE INDEX command? Will that then create an INDEX that is permanently LANGIDSHR?

So then can I end my session, bring up a new session (without LANGIDSHR), use my index and it's magically still in LANGIDSHR sequence? Also, that only seems to address case sensitivity. What tells it to use the alternate collating sequence that corresponds to CCSID 819, for example?

Joe


Joe,

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...

HTH,

Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 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 [javascript protected email address].