×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
From: David Gibbs
Joe Pluta wrote:
Have you tried SRTSEQ(*LANGIDSHR)? As I understand it, it's exactly
what
you're looking for: indexing mixed case fields using a language
sensitive
sequence.
I see the parameter your talking about ... but to be honest, I'm can't
see how it's used.
Is this something that's used in association with an alternate collating
sequence table?
Well, I've only used it in English, but if I specify *LANGIDSHR, it will use
the language ID of my job to sort the data. If I create two identical
logical files, adding ONLY the SRTSEQ(*LANGIDSHR) parameter to the compile,
I end up with this:
No SRTSEQ:
Joe
Joe Cocker
Joe Schmoe
JOE
JOE SMITH
SRTSEQ(*LANGIDSHR):
JOE
Joe
Joe Cocker
Joe Schmoe
JOE SMITH
I'm guessing here, but I think there are internal collating tables for
mixed-case English just like there are for other languages, and when you
select *LANGIDSHR, it uses the appropriate table. You can change which
internal table it uses by specifying the language ID.
One thing weird, I think *LANGIDSHR sorts numerics BEFORE alpha.
Joe
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
