Re: Phantom Tapes
1998-12-09 12:38:39
>
Hi Jackie,
I believe I had a similar experience, except I was using the Magstar
3570. Here is what happened to me and how I resolved it.
After loading the Atape driver, and configuring my tape library,
I ran the following command to check in my tapes:
adsm>CHECKIN LIBV MAG3570LIB SEARCH=YES STATUS=SCRATCH
CHECKLABEL=BARCODE
a query of the library showed that I had 10 tapes available
with a status of scratch.
adsm>q libv
libr name volume name status last use
---------- ----------- ------ --------
MAG3570LIB 01C9999 Scratch
MAG3570LIB 01C9999 Scratch
.
.
.
Once I tried to utilize the tapes, the adsm server would go through and
change the status of each tape to private, and last use to data.
When i audited the library, the adsm server would remove each of the
volume from the library.
A fellow ADSM colleague advised that the tapes didn't have a label on
the tape itself, and that I should first label the tape. The command I
ran was:
adsm>LABEL LIBV MAG3570LIB SEARCH=YES STATUS=SCRATCH CHECKLABEL= BARCODE
OVERWRITE=YES.
I immediately ran an audit libr, and the volumes remained in the
library.
Hope this helps.
>Strange happenings with tapes staying in libv with a status of private
and last use of data. Theses tapes however: belong to no storage pool
and have no data on them. We are at the latest release of Atape driver,
ADSM 3.1.1.3 server on Aix. The only way I can get them back to scratch
is to assign them to a dummy storage pool and delete them. Has anyone
seen this. We have a 3575 L32.
______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com
|
|
|