|
At 04:20 08/03/2000 , Brendan Bispham wrote: >You might want to check the archives, but I believe the concesus was to >remove the logical file members, increase the PF, and then ADDLFM the >members again. >Shouldnt they be changed to *MAX1TB as well? >I think speed can be improved with SHARE(*YES). The share attribute is not what's needed here. You're thinking of shared access path. SHARE(*YES) gives you (by default) a shared cursor, which can cause major problems if existing apps are using the files, and they were not designed to use a shared cursor. Access path sharing can be achieved by creating the logicals with the largest number of key fields first (no includes or omits). Other files that might use just the first part of the key will then share the access path automatically. There are also some caveats about *MAX1TB. It is generally true that the 1TB indexes perform better, but there are some conditions where they do not. Hopefully someone who is more familiar with that issue can comment on the specifics. Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.