Good morning,

I´m on 5.1.7.0 on w2k SP3 and DLT7000 drives in STK9710.

I used dsmlabel 'dsmlabel -library=lb0.0.0.8  -drive=mt3.0.0.4,1032
-drive=mt4.0.0.4,1033 -drive=mt5.0.0.6,1034 -drive=mt8.0.0.6,1035 -keep
-overwrite -barcode'.
All went fine, then I used 'checkin libv stk9710 search=yes checkl=barcode
status=scratch'  and added all new tapes to my scratch pool.
And  now when TSM try to use thoose tapes.... grr.

10/17/2003 16:48:30      ANR8337I DLT volume 000002 mounted in drive DRIVE4
                          (mt5.0.0.6).
10/17/2003 16:48:30      ANR1340I Scratch volume 000002 is now defined in
storage
                          pool 9710COLLO.
10/17/2003 16:48:30      ANR1411W Access mode for volume 000002 now set to
                          "read-only" due to write error.
10/17/2003 16:48:35      ANR1341I Scratch volume 000002 has been deleted
from
                          storage pool 9710COLLO.
10/17/2003 16:49:05      ANR8468I DLT volume 000002 dismounted from drive
DRIVE4
                          (mt5.0.0.6) in library STK9710.

I did a Checkout of my dsmlabled tapes and issued 'label libv stk9710
search=bulk labels=barcode checkin=scartch overwrite=yes'.
It works!

The reason why I first used dsmlable was the tapes that I got from another
site was already labled with with same volumenames that existed
 in my TSM server. So I had to scatch the volumename and define new.

Any thought why dsmlabel didnt work i.e. why did I have to use 'label libv'
too?


//Henrik


-------------------------------------------------------------------
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.