Hi, Eric -

For better or worse, this is "historically normal" behavior for the
product - I see it a lot.
A tape will be busy as output for a client session, or be in the
process of dismounting,
and the server will revert to a scratch tape for the second session
which might
otherwise have used that tape. Future sessions may all be singular, and
the second
tape will simply languish. I have an advisory in ADSM QuickFacts for
administrators
to periodically query for such orphans, as a cause of "tape leak". It
would be nice if
the product better dealt with such tapes, but...

   Richard Sims

On Sep 8, 2004, at 5:01 AM, Loon, E.J. van - SPLXM wrote:

Hi *SM-ers!
I have found something very strange in our TSM tape utilization.
I found several primary storage pool tapes which should be used for
data,
but which are not.
For example, one tape has a read/write, filling status with a
utilization of
about 3% and about 23% reclaimable. However, the last written date is
September 15, 2003!!!
I checked all other servers and they all have several tapes in a
filling
state with a last written date several months ago.
I really cannot explain how this is possible. Does anybody know what's
wrong
here? The tapes have no error state, nor did they have in the past.
Thank you very much for any reply in advance!
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines