How many digits of the barcode are you passing to TSM?

Is there a potential for a volser conflict?

I seem to remember a problem where: A tape is mounted in a tape drive,
having come from slot 1024, and then a checkin puts a tape in slot 1024.
When the tape unmounts, TSM or the library attempts to put away the tape
in slot 1024 (which is already full). IIRC, this was fixed in a later
version of the TSM code.

[RC] 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Stephan Boldt
Sent: Wednesday, May 27, 2009 12:47 AM
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


DISCLAIMER:
This message is intended for the sole use of the addressee, and may contain 
information that is privileged, confidential and exempt from disclosure under 
applicable law. If you are not the addressee you are hereby notified that you 
may not use, copy, disclose, or distribute to anyone the message or any 
information contained in the message. If you have received this message in 
error, please immediately advise the sender by reply email and delete this 
message.