As to alt seq- remember that with case-insensitive, you really don't have anything that is exactly ASCII or whatever.

I have played a little with changing language, such as using Romanian vs.ENU. Interesting things happen with the letters J and Y - I forget the language I played with, but you can imagine.

On 3/27/2012 9:40 AM, Joe Pluta wrote:
On 3/27/2012 9:17 AM, Charles Wilt wrote:
On Tue, Mar 27, 2012 at 10:05 AM, Joe Pluta<joepluta@xxxxxxxxxxxxxxxxx> wrote:
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
No, as there's no way for you to explicitly "use the index"

If you configure your new session for LANGIDSHR, when you do a select
and specifiy ORDER BY indexedColumn, the system will implicitly use
the LANGIDSHR index you created.

Also, that only seems to address case sensitivity. What
tells it to use the alternate collating sequence that corresponds to
CCSID 819, for example?
Same applies AFAIK, but I've never tried it.

Okay, that removes the "magic black box" aspect which always makes me
uncomfortable. This makes much more sense. Having an index (or not) is
really not the issue; if the job is set for LANGIDSHR, the SQL engine
will use such an index if it exists. The problem is to get an ODBC job
to use LANGIDSHR. Or CCSID for that matter.

To set LANGIDSHR on a JDBC connection I can use "sort weight=-shared"
but I'm unsure of how to set the language or CCSID to get ASCII
collating sequence.


This thread ...


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

This mailing list archive is Copyright 1997-2020 by 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].