"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/18/2012
06:28:41 PM:

> > > In the past we've never had to restart TSM to add a new drive.  As
> > > long as the drive was discovered and available at the AIX layer, we
> > > could define the new drive.  Has this changed with v6.2.x?
> >
> > It's my experience that any change to the library (adding slots or
drives)
> > requires cycling TSM before it can access the new resource.
>
> Seriously?  Is this behavior due to changes in TSM 6.x, or has it
> always been this way for SCSI-style (smcX) libraries?
>
> I've never had this issue with my 3494 library and any TSM version
> from ADSM 2.1 through TSM 5.5.

Our libraries are 3584 scsi libraries, which are different animals from
3494 libraries.  Sorry, I should have said that.

Any time we have changed the physical library it has required us to bounce
TSM so the new slots EA and/or drive EA are available to TSM.  In our
case, that's our library manager tsm instance.  We are still on v5.5, but
I've seen nothing that would indicate that v6+ is any different.



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.