Re: SQL options precedence for SQLRPGLE

On 19 Jun 2013 10:24, Luis Rodriguez wrote:

On Wed, Jun 19, 2013 at 12:43 PM, Josh Diggs wrote:

<<SNIP>> problem is that the sort sequence *LANGIDSHR is specified
somewhere, but not explicitly by us. This has performance
implications of the negative kind, which business users do not
like.

Please be aware the sort sequence can be set at the time of your
table creation. Check, for example, the RUNSQLSTM options (F13).

F13=Services is for the STRSQL. The SRTSEQ parameter of RUNSQLSTM is available for similar. Or the SRTSEQ option of the SQL SET OPTION.

FWiW: The meaning of the Sort Sequence (SRTSEQ) to the CREATE TABLE statement is limited to the keyed Access Path of any constraint that is added; during the CREATE TABLE or a later ALTER. The SRTSEQ [in combination with the Language Identifier (LANGID)] of the database *FILE, as presented by DSPFD [as set from the SRTSEQ option established for the SQL environment in which the CREATE was performed], determines what is the Sort Sequence applied to the CONSTRAINT added during an eventual ALTER TABLE ... ADD CONSTRAINT request.