×
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.
Title: Problems with Query on V4R5
Ever since REUSEDLT
was introduced I've been adopting it as much as possible. Reusing deleted
records makes arrival sequence useless, so I've had to depend on explicit sorts
for everything. I can remember a few times in the past (probably since
V4R3) where a query sorted on a field that was beyond the requested sort in the
query definition. In each case there was another access path supporting
that sort so I assumed that the query optimizer was using that path behind the
scenes.
The consensus of
list replies and IBM is that you're hosed and I tend to agree, but you might
look for an access path that's causing your problem. Also, are you
performing a SELECT on the text field that might inspire the query optimizer to
sort on that field?
-Jim
This mailing list archive is Copyright 1997-2025 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
