The SRTSEQ of SET OPTION doesn't change the table, so far as I know. It will use an existing index that has the right sort sequence, if it exists. Otherwise, it creates the index or maybe does an internal sort first.

As to releases, I started using LANGIDSHR while developing toV5R1- it still does nicely.


On 3/27/2012 8:49 AM, Luis Rodriguez wrote:

You are right about CQE vs SQE - that was changed at V5R4 - I ran into
that with one of our products where we have case-insensitive searches.
Of course, I shouldn't be at V5R3 :-(, but sometimes you must do with what
you have...

Also, IIRC, *Set Option* has a SRTSEQ clause. Don't know if that can change
the table's properties at run time.


Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries

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