Also consider setting different label prefixes (this is done by devclass) for 
each server

>>> Gabriel Wiley <wileyg AT US.IBM DOT COM> 15/03/2002 13:13:29 >>>
It also might help if you use different Volsers for each TSM server.

I have an ATL with 12 drives, 4 per server with Volsers Axxxxx for Server1
Bxxxxxx for Sever2 and Cxxxxxx for Server3 ..


Gabriel C. Wiley
ADSM/TSM Administrator
AIX Support
Phone 1-614-308-6709
Pager  1-877-489-2867
Fax      1-614-308-6637
Cell       1-740-972-6441

Siempre Hay Esperanza




                      "Davidson, Becky"
                      <Becky.Davidson@S        To:       ADSM-L AT VM.MARIST 
DOT EDU 
                      LBG.COM>                 cc:
                      Sent by: "ADSM:          Subject:  Re: Multiple TSM 
Servers on Same Machine
                      Dist Stor
                      Manager"
                      <[email protected] 
                      .EDU>


                      03/14/2002 05:49
                      PM
                      Please respond to
                      "ADSM: Dist Stor
                      Manager"





We ran option 1 for a long time both with twintailed scsi and a san but
have
now mostly switched to option 2.  We shared all of the drives and
frequently
ran into problems where tsmsvr1 had a drive and tsmsvr2 tried for awhile to
use it and then marked it unavailable until I marked it online.  With 1 you
definitely need different catagories and you have to be careful.  It makes
it easier if you use 100's for one and 200's for the other because I want
to
say the number above the scratch is automatically saved for the same
systems
private or vice versa and it can get you in trouble.  The best explaination
I have run into on how to set up the library manager is in the LTO Open
Redbook and you just modify what you need for 3494.

Good luck
Becky