|
Charly, I looked at the access paths earlier and they appear to be set to *MAX1TB. I think I forgot to mention that much of this process is vendor code written I believe in RPGIII. Many are RPT and I suspect some may actually be RPGII. -----Original Message----- From: Charly Jones [mailto:charly309@xxxxxxxxxxx] Sent: Tuesday, June 24, 2003 12:27 PM To: midrange-l@xxxxxxxxxxxx Subject: RE: SMP experiences >There is a lot of LF updating I believe. We have three files that get hit >pretty hard every night. The smallest has 94+ million records with 21 >indexes and the largest is over 400 million with 6 indexes. Rick -- If you have more than one job accessing these files you might want to check that you are using the new improved terabyte indexes for all the access paths built over these three files. If you are using the gigabyte indexes the locking during index maintenance is at the file level. The new improved terabyte indexes lock at the page level. It is controlled with the: Access path size (ACCPTHSIZ) parameter either *MAX4GB or *MAX1TB. When you change it, it will rebuild the access path. -- Charly Merlin Inc Box 640 Gig Harbor WA 98335 USA 253 265-6244
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.