Wanda,
I have had similar problems with 'lost tapes' in my 3583.
A full checkout and checkin was the suggested solution
by IBM last time I asked (a long time ago now), but I found
doing a
checkin libv LIBRARYNAME search=yes checkl=b stat=pri
will bring many tapes back into the fold. I do a 'q libv'
before and after, and use a spreadsheet to find the differences. Is it a
pain? Yes. I don't do it often enough
to get it over my thresh hold of pain so that I automate it.
> -----Original Message-----
> From: Prather, Wanda [SMTP:Wanda.Prather AT JHUAPL DOT EDU]
> Sent: Tuesday, June 01, 2004 3:25 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Question for you 3494 gurus -
>
> Yee ha!
> That worked - it took the tape from the Recovery cell, put it back in its
> home slot, and changed its category back to the correct TSM category.
> THANKS PAUL!!
>
> -----Original Message-----
> From: Thorson, Paul [mailto:Paul.Thorson AT McKesson DOT com]
> Sent: Tuesday, June 01, 2004 4:10 PM
> To: 'Prather, Wanda'
> Subject: FW: Question for you 3494 gurus -
>
>
> Hi Wanda,
>
> I have to e-mail this direct because my Exchange account does not allow
> forum postings.
>
> If you can get your hands on the tape, try putting it in the recovery
> cell.
> You can pause the 3494 and look in its home slot (do a search on the
> operator menu). The tape, if stuck in a drive, may have been placed
> outside
> the ATL too. If you can get your hands on it, open up the 1st frame
> (L-frame) and place it in the top left cell (recovery cell). Then close
> the
> frame door(s), and put the ATL back in AUTO mode. After inventory is
> complete, the LM should try to "fix" the tape.
>
> The 3494 library manager has a very narrow path for correct volume
> handling
> - once outside the box (so to speak), the best bet is to put a tape in the
> recovery cell, and hope for the best.
>
> If that doesn't work or you cannot find the tape, you could try to power
> cycle the LM or perform a full inventory to reconsile the contents.
>
> Good luck.
>
> Regards,
>
> - Paul
>
> -----Original Message-----
> From: Prather, Wanda [mailto:Wanda.Prather AT JHUAPL DOT EDU]
> Sent: Tuesday, June 01, 2004 2:56 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Question for you 3494 gurus -
>
>
> Hi Dwight!
>
> No intervention currently. Gripper is working, have entered and ejected
> tapes this afternoon.
> From the TSM activity log, it appears this was an eject (or maybe a
> gripper)
> failure a couple of weeks ago.
> I wasn't here that day, somebody apparenlty got the library working again
> but this tape was left in a strange state.
>
> Everything ELSE has been working fine since, just this tape is in a
> bizarre
> state.
> I wouldn't have noticed except once a month a do an "audit" of my scratch
> volumes to make sure everybody is accounted for, and this one tape came up
> missing 'cause it is neither marked private or scratch or offsite.
>
> I tried the mtlib -a just now, and get the same error:
>
> Audit Volume Operation failed (errno=5) , ERPA code - 64, Library VOLSER
> in
> use
>
> (Do I need to know what an ERPA is?)
>
>
>
> -----Original Message-----
> From: Dwight Cook [mailto:cookde AT US.IBM DOT COM]
> Sent: Tuesday, June 01, 2004 3:43 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: Question for you 3494 gurus -
>
>
>
>
>
>
>
> have you tried to audit the volume to get things sort of reset ?
> mtlib -l /blah/blah -a -Vxxxxxxx
> also does a query of the library show anything such as a gripper not
> available ?
> tape might have been on its way out of the library and the gripper failed
> to be able to release it...
> or any other intervention on the atl ???
>
> Dwight E. Cook
> Systems Management Integration Professional, Advanced
> Integrated Storage Management
> TSM Administration
> (918) 925-8045
>
>
>
>
> "Prather, Wanda"
> <Wanda.Prather@JH
> UAPL.EDU> To
> Sent by: "ADSM: ADSM-L AT VM.MARIST DOT EDU
> Dist Stor cc
> Manager"
> <[email protected] Subject
> .EDU> Question for you 3494 gurus -
>
>
> 06/01/2004 01:50
> PM
>
>
> Please respond to
> "ADSM: Dist Stor
> Manager"
>
>
>
>
>
>
> OK, I"ve never seen this one before!
>
> I was trying to track down a missing TSM scratch tape.
> The library manager DB SEARCH says it is IN the 3494, but it's current
> category code is FF10, which is the EJECT category.
>
> mtlib -qV -Vnnnnnn -l libname
>
> shows "volume in process of being ejected".
>
> Well, it isn't! And nothing shows up in the eject queue on the library
> manager.
> I have ejected other tapes today with no problem.
>
> And if I use mtlib to try and CHANGE the category code again, I get
> "Change
> Category operation failed, volume in use".
> It has been this way for weeks, based on the last entry I see for it in
> the
> TSM activity log.
>
> Any idea how I fix this?
>
> Thanks!
|
