You are correct.
However, my personal preference is to use the SET OPTION in the source rather than depending on the
next guy to specify the correct options on the CRTSQLxxx commands.
CINTAS Corporation - IT 92B
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Walden H. Leverich
Sent: Thursday, July 31, 2008 2:32 PM
To: Midrange Systems Technical Discussion
Subject: RE: Case insensitive searching with SQL
For a stored procedure, UDF, or embedded SQL, add the
statement SET OPTION SRTSEQ = *LANGIDSHR
I believe (not on i right now) that SRTSEQ is also an option on the
Also, IIUIC, older releases of SQE cannot use an index marked that way so
you'll be forced down CQE, but I believe that's now resolved (5.4, 6.1,
not sure which? I sure Elvis or Birgitta will chime in :-) )
Walden H Leverich III
(516) 627-3800 x3051
Quiquid latine dictum sit altum viditur.
(Whatever is said in Latin seems profound.)
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.