Re: SQL options precedence for SQLRPGLE -- RPG400-L

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

Subject: Re: SQL options precedence for SQLRPGLE
From: Buck Calabro <kc2hiz@xxxxxxxxx>
Date: Wed, 19 Jun 2013 13:37:31 -0400
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: "RPG programming on the IBM i \(AS/400 and iSeries\)" <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

On 6/19/2013 1:13 PM, Josh Diggs wrote:

Thanks to all who replied. The PRTSQLINF helped. The basic business 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.

WRKSYSVAL QSRTSEQ is where this starts, and it flows through CHGJOB so
you might be able to test *HEX easily enough.
--buck

As an Amazon Associate we earn from qualifying purchases.

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.