×
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.
Good catch. I've read the help on that
If the records must exactly match the current arrival sequence, do not use *RPLDLTRCD.
Apparently if you omit KEYFILE, or use the default of *NONE, it respects the arrival sequence. This is a good thing. There's your safety net right there.
However, if you just know the table doesn't give a rats posterior about arrival sequence, like something which is always accessed by key (item master perhaps), then you can often boost performance by specifying the key with the sequence you use most in your performance critical application. Maybe I'm wording that wrong but what I'm trying to say is that let's say your OrderDetail table has a primary key on it of orderNumber and OrderLineNumber. You could reorg that with KEYFILE(*FILE) to resequence it that order. Or, if you really need it sorted by sales amount descending and you just happen to have an index over it by SalesAmt then KEYFILE(SALESIDX) may be the way to go to get that query to perform best.
Rob Berendt
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.
midrange.com
