Greetings,
        I thought of this same approach, but it doesn't really address
the issue at all.  The times_mounted gets reset to 0 whenever the tape
goes back to scratch.  So times_mounted doesn't track the entire
multi-year history of a tape. I just went and looked at some of our
tapes that are three years old, and the last time they were written to
was a few days ago, and the times_mounted is 2.  According to that
query, that tape looks almost brand new, but I know for a fact we have
been reusing them for three years.
        In our situation it makes even less sense, since we have a
shared library, and the tapes are scratched and then reused by other TSM
instances.  Well, the given instance's point of view on how many times a
tape has been mounted is only since the last time it was grabbed it from
the scratch pool; it doesn't know about any of the times times the other
instances have used it.


Best Regards,

John D. Schneider 
Phone: 314-364-3150 
Cell: 314-486-2359 
Email:  John.Schneider AT Mercy DOT net 


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
TSM
Sent: Thursday, June 19, 2008 4:12 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Antwort: LTO Tape Life

select volume_name,times_mounted from volumes order by times_mounted
desc
This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR
OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the
use of the addressee(s) named above. If you are not the addressee, or the
person responsible for delivering this to the addressee(s), you are notified
that reading, copying or distributing this e-mail is prohibited. If you have
received this e-mail in error, please contact the sender immediately.