Yes, that's what I've done inthe past.  We have a lot more tape drives
since I last upgraded atape.
I've got 2 servers, each with 28 drives on 6 paths.  That's 168 rmt devices
on each server.
Yes, I'm using multipathing.

I've never understood why TSM can't auto-discover paths and drives.  Even
our brain dead HP Omniback
can do that.

Rick





             Ben Bullock
             <bbullock@MICRON.
             COM>                                                       To
             Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
             Dist Stor                                                  cc
             Manager"
             <[email protected]                                     Subject
             .EDU>                     Re: Upgrading atape and atldd


             09/06/2007 02:45
             PM


             Please respond to
             "ADSM: Dist Stor
                 Manager"
             <[email protected]
                   .EDU>






I've always followed their docs and deleted, uninstalled and reinstalled
the drivers. It is not too much of a problem other than sometimes you
need to rename the RMT device names (especially if you are using FC
multipathing to the drives.)

I'd stick with the tried and true.

Ben

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Rhodes
Sent: Thursday, September 06, 2007 12:44 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Upgrading atape and atldd

In reading over the IBM procedure for upgrading atape on AIX (article
1174910), it says to removed the tape and lib devices from AIX (rmdev
-dl fmtX). Is this really necessary?  Can you just drop them to a
defined state (rmdev -l rmtX) for the upgrade so as to not mess up the
paths?  Also, is it really necessary to uninstall the previous version,
or can you just do a smitty upgrade.

Thanks

Rick


-----------------------------------------
The information contained in this message is intended only for the
personal and confidential use of the recipient(s) named above. If the
reader of this message is not the intended recipient or an agent
responsible for delivering it to the intended recipient, you are hereby
notified that you have received this document in error and that any
review, dissemination, distribution, or copying of this message is
strictly prohibited. If you have received this communication in error,
please notify us immediately, and delete the original message.