If your actlog goes back that far, examine it for when you did the MOVE MEDIA command.
I have done this before and it is a bit of a pain. I think after the MOVE MEDIA it
may then want you do do a CHECKIN for the volume. The docs on the command wasn't
clear and I had to play with it to get it right. It works slightly different as I
recall depending on whether tape is empty or has data on it.
If somebody has a good clear procedure on how do do this and make it work right, let
us know.
David B. Longo
Systems Administrator
Health First, Inc. I/T
3300 Fiske Blvd.
Rockledge, FL 32955-4305
PH 321.434.5536
Pager 321.634.8230
Fax: 321.434.5525
[EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 01/04/01 08:51AM >>>
Seems like my problem has not gone away. Here is the error message I get
when I issue a delete vol.
ANS8001I Return code 14 on the command line
ANR2017I Administrator PALMADJ issued command: DELETE VOLUME p50008
discarddata=yes
ANR1425W Scratch volume P50008 is empty but will not be deleted - volume
state
is "mountablenotinlib".
Here is a q vol of that volume:
adsm> q vol p50008 f=d
Volume Name: P50008
Storage Pool Name: FOS-XCH-TAPE
Device Class Name: 3590
Estimated Capacity (MB): 0.0
Pct Util: 0.0
Volume Status: Empty
Access: Read/Write
Pct. Reclaimable Space: 0.0
Scratch Volume?: Yes
In Error State?: No
Number of Writable Sides: 1
Number of Times Mounted: 48
Write Pass Number: 2
Approx. Date Last Written: 11/02/2000 22:31:20
Approx. Date Last Read: 06/05/2000 19:59:26
Date Became Pending:
Number of Write Errors: 0
Number of Read Errors: 0
Volume Location: PAL Tape Rack
Last Update by (administrator): PALMADJ
Last Update Date/Time: 11/07/2000 11:35:29
Here is a q con:
adsm> q con p50008
ANR2034E QUERY CONTENT: No match found using this criteria.
ANS8001I Return code 11.
ADSM Server is rs6k ADSM 3.1.55
Thanks for any help
Jack
-----Original Message-----
From: Keith Davey [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 03, 2001 4:36 PM
To: [EMAIL PROTECTED]
Subject: Re: your mail
What is the percise error message you get when you try to delete volume
<volumename> discard=yes ?
Keith Davey
On Wed, 3 Jan 2001, Palmadesso Jack wrote:
> Kind of quiet today!
>
> I hope this is a simple one. I have some volumes that were removed from a
> 3590 library and then went "unavailable" The volumes are now back in but
are
> all empty. A "q con" for each volume shows there is no data. My problem
is
> how do I make these volumes scratch again? I cannot delete the volumes
> because I get volume cannot be deleted because volume state is mountable
not
> in lib. How do I make these scratch again?
>
> Thanks for any help
>
> Jack
>