1.  A single backups runs to a single volume as perceived by ADSM.  The
first session runs to the first volume allocated to the storage pool.  The
second session runs to the second logical volume allocated to the storage
pool.  The third sessions to the third volume.

With THIS understanding, you can effectively stripe by allocating volume 1
from each drive first, then allocate the second volume from each drive.  You
can see the threads using "show threads".  Run one session, watch iostat,
then start a second and third.  You should be able to see what my
understanding it easy enough (or at least tell me I am wrong)

2.      to see what is used on each database volume, reduce the database
space (reduce log 1000)  and run q dbv f=d.   Before reducing the database,
it will show only the space extended into. (this can also be used when
deleting volumes or migrating)

3.      Migration to tape comes from multiple volumes and is based on the
node being migrate (also the parameters Richard Simms stated yesterday)

4.      Regarding database performance, there a lot of wrong ways to do it
and some right things to do, but the way you set the database up will most
likely depend on your background.  (there is no clear best way)  Any
correction is appreciated.

Jeff Bach
Home Office Open Systems Engineering
Wal-Mart Stores, Inc.

WAL-MART CONFIDENTIAL


        -----Original Message-----
        From:   Richard Sims [SMTP:rbs AT BU DOT EDU]
        Sent:   Thursday, August 30, 2001 12:53 PM
        To:     ADSM-L AT VM.MARIST DOT EDU
        Subject:        Re: TSM DB/Disk Pool - Disk tuning question

        >1) there is no need to have multiple ADSM volumes, one big volume
fine.

        One big volume means one big processing thread, which sacrifices
        parallelism, impairing performance.

          Richard Sims, BU


**********************************************************************
This email and any files transmitted with it are confidential
and intended solely for the individual or entity to
whom they are addressed.  If you have received this email
in error destroy it immediately.
**********************************************************************