Well it was on a 3490e but I had a case where: say I have drives 1, 2,
     3, & 4.

     Tapes would occasionally self destruct.  (become unreadable)

     what was happening was drive 3 could read anything created anywhere,
     tapes created/modded by drive 3 could ONLY be read by drive 3 - the
     other drives would get io errors so ADSM marked the tapes as
     unavailable

     checked microcode, cables, adapters, drive controller....yada yada

     Ran diags until the diag program complained about overtime pay <- JOKE

     CE checked alignment on heads - OK
     CE REPLACED read/write head on drive 3 - PROBLEM WENT AWAY -

     Go figure!

     Also, do 3570's use Atape.driver?  What level are you at?  Had some
     issues with this before too.

     Hope this helps.
     Al Barth
     Scudder Kemper Investments
______________________________ Reply Separator _________________________________
Subject: Re: 3570 errors continued
Author:  Pat Mills <Pat_Mills AT SONYMUSIC DOT COM> at ~internet
Date:    11/4/98 10:22 AM


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