Richard,
 
I was afraid this was the only way out, as you say, there's no way to remove 
just one.  Since earlier this afternoon, I've found another example.  So next 
week, I'll look for more and make sure I'm not killing any DBS volumes offsite.

________________________________

From: ADSM: Dist Stor Manager on behalf of Richard Sims
Sent: Fri 10/5/2007 1:50 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Two tape problems



On Oct 5, 2007, at 2:26 PM, Fred Johanson wrote:

> The Library Manager knows the owner and the last-use and the status.
> The Library Client, i.e., the owner knows nothing about the volume;
> there's nothing in the volhist with that volume name.  "Q vol" returns
> not found.  The volume has never been used on the client.

Fred -

This general type of situation has been seen a few times in the past,
as I remember.
You may have to perform DELete VOLHistory with Type=REMote, as noted
in ADSM QuickFacts.  See past reports in the List archives.  Try
Query VOLHistory with Type=REMote to get a sense of the situation.
It might be some variant situation.  The historic Activity Log might
reveal what happened.

Something analogous occurs in ordinary processing, where a scratch
volume gets associated with a storage pool as a process is about to
take place, but that doesn't get started or is cancelled before the
first I/O, and the volume ends up in limbo.  (The following will
usually find such volumes:
Select * from VOLUMES where STATUS='EMPTY' and SCRATCH='YES' and
PENDING_DATE is NULL)

   Richard Sims