ADSM-L

Re: 3570 errors continued

1998-11-12 18:34:04
Subject: Re: 3570 errors continued
From: Peter Gathercole <peter.gathercole AT VIRGIN DOT NET>
Date: Thu, 12 Nov 1998 23:34:04 +0000
Yes, I have already reported it (at 2.1.5.18 on AIX) and was told that the fix 
would be "sometime in version 3" according to IBM. Don't know for
certain what the APAR number was, however.

Peter Gathercole

Mathew Warren wrote:

> Hello,
>
> Hmm. Thanks for this, I just noticed one of the R/W tabs had popped off of 
> one of our tapes and wondered what would happen if I tried to use it...
>
> Matthew.
>
> >>> "Garin P. Walsh" <Garin_Walsh AT NOTES.SABRE DOT COM> 11/09 12:32 pm >>>
> It might be a long shot but I have had it occur now twice in the last
> month..... Check to see if the read/write tab is still on all the tapes.
> What was happening to me, and it sounds similar, was that a database backup
> was running and it had selected a tape that the r/w tab had popped off of.
> It would mount it, generate an unable to mount error, put the bad tape back
> in its slot, wait 60 seconds, and then try again (IBM support - could the
> db backup code be modified to try a different tape in the event of a mount
> failure?). Because the tab had popped off ADSM was unable to mount it for
> write. It would bounce like this for a long time. While this was happening
> I was getting mount failures on other processes because the "drive was
> full" - near as I could tell, it was just because the db backup process
> still owned the drive and hadn't released it. I did a checkout on the tape
> and as soon as the db backup process mounted another tape the "full drive"
> message went away and all was fine from then on.
>
> If nothing else it is worth a shot.
>
> Garin Walsh
> The Sabre Group.
>
> Pat Mills <Pat_Mills AT SONYMUSIC DOT COM> on 11/04/98 01:22:46 PM
>
> Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
>
> To:   ADSM-L AT VM.MARIST DOT EDU
> cc:
> Subject:  Re: 3570 errors continued
>
> We and IBM have been working on a 3570 problem for about 3 weeks now.  Of
> course the first culprit is always microcode.
>
> The level we are now running on 2 3570s is an unreleased version.
>
> EC C70552
> LINK D1I4_22F
>
> Didn't fix my problem. But why would it? It works for a year then self
> destructs? I don't think so.
>
> One 3570 works the other doesn't. When I do a "audit libr LIB1", after it
> reads the label on the second tape, doesn't matter what position that
> second tape is in, and fails with a ANR8300E.
> Description= The destination slot or drive was full in an attempt to move a
> volume.
>
> Hardware? Software? Hardware?...........
>
> I'm beginning to think we'll never know.
>
> Pat
>
> ** IMPORTANT INFORMATION **
> This message is intended only for the use of the person(s) ("the Intended 
> Recipient")
> to whom it is addressed. It may contain information which is privileged and 
> confidential
> within the meaning of applicable law. Accordingly any dissemination, 
> distribution, copying
> or other use of this message or any of its contents by any person other than 
> the Intended
> Recipient may constitute a breach of civil or criminal law and is strictly 
> prohibited.
>
> If you are not the Intended Recipient please contact the sender and dispose 
> of this email
> as soon as possible. If in doubt contact the Tibbett & Britten Group Network 
> Administration
> Department on 01707 391010 (UK).
<Prev in Thread] Current Thread [Next in Thread>