×
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.
I have very little data that was dependent on arrival sequence. Normally
limited to EDI exchange files.
As far as crossing my fingers and hoping that a select without an order by
would bring it up in arrival sequence, I've never found having to use the
order by clause to be an inconvenience. Nor hoping that a DSPPFM would be
orderly. On those that I had some mild care that the DSPPFM would bring
it up in some order I used the KEYFILE parameter on RGZPFM. Using the
KEYFILE parameter may increase performance because you can get better
blocking if the file is sorted by a popular access path. For example if
you are processing a table where the active record code is '1' and the
order of the item number then using an index by active record code and
item number as the KEYFILE parameter in RGZPFM should assist in that
blocking.
I would think that without reusing deleted records you may have a
performance hit due to the need to create extents as rows are added.
Rob Berendt
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
