An approach that I have used is to first ask, why so much disc io?
 
Use glance and/or filerpt to build a short list of the most accessed files.
 
Most of the time these files will be TurboImage data sets. Use HOWMESSY or
DBLOADNG to check out the data bases. The master data sets should be
examined for max blocks. Detail data sets should be examined for elongation
of chains (including the delete space chain). And of course any sorted
paths are always a suspect for creating unwanted disc io.
 
hth
 
 
 
 
**************************************************************************
********* __                __  * *                              *********
******** / /               / / ** **   Michael C. Hornsby         ********
******* / /               / / *** ***   President                  *******
****** / /___ ______ ____/ / **** ****   Beechglen Development Inc. ******
***** / __  // __  // __  / ***** *****   5576 Glenway Avenue        *****
**** / /_/ // /_/ // /_/ / ****** ******   Cincinnati, Ohio 45238     ****
*** /_____//___  //_____/ ******* *******                              ***
**        __  / /        ******** ********    Phone: (513) 922-0509     **
*        / /_/ /        ********* *********    Fax:   (513) 347-2834     *
        /_____/        ********** **********    Net: [log in to unmask]
**************************************************************************