You don't need to generate this list and do the CHECKIN for each library 
clients' tapes with OWNER...Just checkin all the tapes in
the library as PRIVATE. At this point they will show with no owner. Then on the 
library client run an AUDIT LIBRARY. It seems that
the entire volume inventory from the client is exchanged with the LM. Tapes 
checked in to the library are then changed to the OWNER
of the client and a volume history entry of TYPE=REMOTE is created for each 
volume defined to the client. Do this from each of the
library clients and the LM will be in-sync. Then a select command can be run to 
list all the library volumes in private status
without an owner. These are then probably scratch tapes and you can UPD LIBV 
STATUS=SCRATCH.


Bill Boyer
DSS, Inc.

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Suad Musovich
Sent: Tuesday, March 20, 2007 6:27 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Moving Library Owner/Manager

There's not a single tasklist you can work on because of differing environments 
(are both TSM servers using the libraries
themselves? is there non-standard inventory... like backupsets?)

The last time I did it, it was something like this.

On the old Library Manager (LM)...
- Identify(generate a list) and checkout (rem=no) all Private volumes, from 
that library.
- Then do the same with scratch carts.
- Delete the paths/drives/library definitions

Then, if required, make the new TSM server the library control (if the library 
needs to record which host is the LM)

On the new LM ...
- Define the library/device class/drives/paths (remember to add all remote TSM 
server paths)
- Checkin all private carts (from the list, you generated, including which TSM 
server is the owner)
- Then the checkin all scratch carts.

On the old LM ..
- define shared library with -primarylibman is the new LM

Then you need to check if any carts thats are in inventory but did not 
successfully get checked in (the most common examples are
backupsets and DB backups.

I ended up doing a lot of pre-work(migrations etc) and needed to draft quite a 
detailed implementation/backout plan, as the
enviroment was non trivial.

If you have multiple TSM servers sharing a library, I would personally define a 
dedicated TSM LM instance (maybe on a separate port)
that you can easily move with minimal planning, in future.

Cheers, Suad
--

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 21/03/2007
05:36:37 AM:
> We are working to replace our two AIX TSM servers (old, slow, still
using
> SSA disk, etc) with new x86/Linux boxen.
>
> Unfortunately, the tape library owners/managers are these two AIX boxes.
>
> Has anyone here gone through changing which TSM server owns a tape
> library, that can offer some hints, tips, suggestions ?
>
> How did you accomplish this?  What steps did you take ahead of time?