If the original filling tape is in use, and another session or process
needs to write, The system will select a new scratch.

Look back in your activity log to see your tape mount activity.
You can probably find the answer there. 

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Chris Lenssens
Sent: Tuesday, April 10, 2007 2:35 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: from SEZ


Hi,

 

Info: TSM V5R2L2.0, Sun Solaris, StorageTek L20 LTO2 drives with LT02
tapes ... and I'm not a specialist in TSM

 

First:

In the Sequential Access Storage Pool I've got a pool with an number of
tapes in.  Sometimes at the morning a scratch tape is added to the pool
using a small number of %util (0.4%) although there is a tape in that
pool with a %util of 34% and 0%reclamation;  so data can be added to
this tape (readwrite, no problem with the tape, I'm sure).  In that case
I do a move data on a storage pool volume and TSM takes the 34%-util
tape, the 0.4%-util tape become scratch.  Does someone know the reason
of taking a scratch tape instead of filling (further) the 34%-util tape?


 

Second:

Last week I've checked in 4 brand new tapes from a brand new pack. After
the first use of the tapes, 3 of 4 tapes become 'readonly' and
thereafter 'unavailable'.  Could be a problem with the tapes?  But my
care is how to treat them and to save the information on those tapes?
I've already done an audit vol fix=yes but that takes hours and I
cancelled the process.

 

Thanks in advance.

 

Chris Lenssens

ICT-A.Z Sint-Elisabeth Ziekenhuis