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, that removes the "magic black box" aspect which always makes me
Okay, bear with me, I'm old and slow<grin>.Yes
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 (withoutNo, as there's no way for you to explicitly "use the index"
LANGIDSHR), use my index and it's magically still in LANGIDSHR
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. WhatSame applies AFAIK, but I've never tried it.
tells it to use the alternate collating sequence that corresponds to
CCSID 819, for example?
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