Hi Wil,

Take a look at the activity log, some time before your checkout
operation, and search for that tape number : you'll find out which
process was using it .. I would suspect some reclamation process or too
long mount retention for the devclass associated to your library.
HTH.
Cheers.
  
Arnaud 

************************************************************************
******
Panalpina Management Ltd., Basle, Switzerland, CIT Department
Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone:  +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion AT panalpina DOT com
************************************************************************
******

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
will aire
Sent: Wednesday, 10 August, 2005 13:17
To: ADSM-L AT VM.MARIST DOT EDU
Subject: SUSPECT: (MSW) DR copy volume not ejecting

Hi,
We currently run TSM server 5.2 and have customised the system for DR
using SQL and korn shell scripts. Works o.k. We've recently been running
low on Scratch tapes, and occassionaly i add bits of new scratch in
five's sometimes ten. The problem i have been experiencing lately is
when we eject the copy volumes for offsite storage sometimes one of the
tapes in the list would not get ejected. The activity logs shows tape
being used " i.e vol xxxxx currently being used". On one occassion i
noticed that a combination of low scratch and an overun of backup of
primary_stgpool to copy_stgpool would retain a copy volume and not
release it for offsite storage. But what I have noticed recently is
volume xxxx not ejecting even though backups of primary_stg to
copy_stgpool was not running.
Can you please explain

Wil