Reworking access paths outside of a specific creation script can have
subtle impacts; even potentially severe outcomes, for example looping in
native I/O during updates to key values. There are also [potential]
ramifications to memory usage, storage, and SMAPP for any changes. The
impacts of sharing by create or restore, and reordering restore/recovery
is typically overlooked. A tool that generates a *MIN storage and
number of access paths [to be used in the initial design of a database;
I would discourage use on an existing database file network] does seem
like a nice feature. However simply performing save, delete, restore,
and DSPDBR to review the order for creates would likely be generally
sufficient. YMMV.
This mailing list archive is Copyright 1997-2026 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
