Thanks for the reply. I already have things configured like this.

What I was hoping for was zOS/MVS sysplex sharing smarts (for you
mainframe folks).  With a properly configured sysplex, the drives are
configured and online to all systems at the same time and the OS figures
out which drive is in use by which system and which drives are available
and choses acordingly, not stepping on any other system.  I was hoping the
SAN type libraries were smarter and that  multiple TSM library managers
could just figure out what drives are available and use them accordingly.

I wanted to avoid an all-or-nothing reconfiguration since I need to move
library management/ownership to my new TSM server (phasing out the old AIX
server currently owning the 3583's) and having to reconfigure all TSM
servers that currently share the libraries.



"Stapleton, Mark" <mark.stapleton AT BERBEE DOT COM>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
07/26/2007 11:33 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] Sharing a 3583 library






From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Zoltan Forray/AC/VCU
> I have never shared a 3583 library and drives between multiple TSM
servers
> that will act as library managers/owners.  I have only done this with
my
> 3494.
>
> Is there anything special about how I should configure a second TSM
server
> that I want to take control over a 3583 library ?  Is it basically the
> same process where the library is defined with unique category codes
and
> the drives are transfered to the new server and paths are changed to
use
> the library manager server as a client ?
>
> Or can both TSM servers coexist and share the drives between them ?

If you set up a library manager/library client configuration, the
library will never know the difference, since all requests to the
library are sent by the library manager.

There are no category codes for the 358X library family. If you
physically share the library between multiple servers you would have to
dedicate drives to each server. If you do the library manager/library
client setup, you don't have that issue. The library manager decides
which drives are being used and transfers data and metadata to the
library client machine. Just follow the directions in the TSM
Administrator's Guide on how to set it up.

--
Mark Stapleton
Berbee (a CDW company)
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com