ADSM-L

Re: [ADSM-L] Preventing TSM from using a certain library port

2009-05-27 16:00:09
Subject: Re: [ADSM-L] Preventing TSM from using a certain library port
From: Henrik Vahlstedt <SHWL AT STATOILHYDRO DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 27 May 2009 21:58:35 +0200
So If i understand you correctly.
Barcode reader and gripper works perfectly on all slots exept one. 
Tapeutil can read the volumelabel in the faulty slot.

Can the library read the label if the tape is stored and checked in from
a mailslot?
And you sure that 3583 volume inventory is up to date, and is matching
TSM library volume inventory?


//Henrik

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Stephan Boldt
Sent: 27. mai 2009 16:13
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Preventing TSM from using a certain library port

Hello Henrik,

I cannot see how this should solve the problem. If the library can't
read the tape's barcode (or can't store it in its database, whatever the
reason is), an 'audit library' command would tell TSM that the slot's
empty and tsm would not checkin the volume. But it would try to move
another volume into this slot, when checking them in from the
mailslot...

Maybe I just didn't get the point of your idea...

kind regards,
Stephan

On Wed, May 27, 2009 at 10:06 AM, Henrik Vahlstedt
<SHWL AT statoilhydro DOT com>wrote:

> Run an 'audit library "3583" checkl=barcode' to update library 
> inventory in TSM and a 'checkin libv "3853" search=yes checkl=barcode
stat=pri'.
>
> Let us know if the problem presists after the two commands have run 
> successful.
>
> Thanks
> Henrik
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of Stephan Boldt
> Sent: 27. mai 2009 09:47
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Preventing TSM from using a certain library port
>
> Hello,
>
> our IBM 3583 library seems to have a problem using a certain port.
> Sometimes we get a "slot obstructed" error message because the library

> tries to put a tape into a slot which is already filled with another 
> tape. Looking into the librarys slot information reveals that it 
> assumes this slot is empty! First I thought the cause would be the 
> tape itself / its barcode. But after removing this tape from the lib, 
> the "slot obstructed" problem still occurres with the same slot but a 
> different tape.
> Whatever the cause is, is there a way to tell TSM _not_ to use this 
> slot, even if its empty? Is my assumption right that TSM and not the 
> lib decides where to put a tape when checking it in or removing it 
> from a tapedrive? But when does TSM get the information about which 
> slots are present in a library? During an "audit library"?
>
> Thanks in advance,
> Stephan
>
>
> -------------------------------------------------------------------
> The information contained in this message may be CONFIDENTIAL and is 
> intended for the addressee only. Any unauthorised use, dissemination 
> of the information or copying of this message is prohibited. If you 
> are not the addressee, please notify the sender immediately by return 
> e-mail and delete this message.
> Thank you.
>


-------------------------------------------------------------------
The information contained in this message may be CONFIDENTIAL and is
intended for the addressee only. Any unauthorised use, dissemination of the
information or copying of this message is prohibited. If you are not the
addressee, please notify the sender immediately by return e-mail and delete
this message.
Thank you.