We have 4 3590 tape drives - which are in a 3494 robot which are
constantly wanting to be cleaned as well - also logging tape errors
tape_error1 occasionally. I think our CE has updated us to the most
current microcode - but I'll ask him just to be sure.

LABEL:          TAPE_ERR1
IDENTIFIER:     4865FA9B

Date/Time:       Sun Aug  2 11:49:27
Sequence Number: 7489
Machine Id:      000066218900
Node Id:         spf2n9sw
Class:           H
Type:            PERM
Resource Name:   rmt2
Resource Class:  tape
Resource Type:   3590
Location:        00-11-01-0,0
VPD:
        Manufacturer................IBM
        Machine Type and Model......03590B1A
        Serial Number...............000000029494
        Device Specific.(FW)........9548

Description
TAPE OPERATION ERROR

Standard input

lsdev -Cc tape
rmt0  Available 00-03-01-1,0 IBM 3590 Tape Drive and Medium Changer
rmt1  Available 00-03-01-3,0 IBM 3590 Tape Drive and Medium Changer
lmcp0 Available              LAN/TTY Library Management Control Point
rmt2  Available 00-11-01-0,0 IBM 3590 Tape Drive and Medium Changer
rmt3  Available 00-11-01-2,0 IBM 3590 Tape Drive and Medium Changer

rmt0              00-03-01-1,0      IBM 3590 Tape Drive and Medium
                                      Changer

        Manufacturer................IBM
        Machine Type and Model......03590B1A
        Serial Number...............000000029332
        Device Specific.(FW)........9548
        ----------
        From:  Garin P. Walsh [SMTP:Garin_Walsh AT notes.sabre DOT com]
        Sent:  Tuesday, August 04, 1998 10:06 AM
        To:  ADSM-L AT VM.MARIST DOT EDU
        Subject:  Re: IBM RS6000 F50 4-way

        We have a 4-way F50 w/ a 3575 L12 (2 3570 B type drives) and
have been very
        happy so far - running AIX 4.2.1 with the latest TCP/IP and tty
patches,
        ADSM 3.1.1.3, 332 MHz processors, 512 MB RAM, and 4 of the new
9.1 GB SCSI
        drives. 100+ clients (mix of NT, 95, VMS, and AIX). Very fast.
The only
        problems encountered so far are that the system firmware code
installed on
        the F50 when the machine shipped was not a new enough version to
support
        the 332 processors - We had intermittent (every 2 weeks or so)
crashes with
        a SRN that indicated an I/O planar failure. The tech that
replaced the
        planar installed one with even an older firmware level - IBM was
surprised
        it even booted - it didn't run long though. After the firmware
update not
        another crash - now it has been almost 19 days of uptime and
counting.

        One annoying thing so far about the tape drives though is that
one of the
        two seems to want to be continuously cleaned. I was told that
there was a
        firmware update for the drives to address a possible cause of
this problem
        but I can't find anyone who knows about it - Anyone out there
have a
        similar problem and a solution???

        Also, from newbie experience, I would want a minimum of three
drives in the
        future. It seems that whenever there is a long running process
that is
        using two of the drives, ADSM wants to do a database backup and
that has
        precedence - I am currently evaluating point in time recovery
and have the
        database backup trigger enabled - aborting the long running
process.





        Karl Roessmann <roess AT AND.MPI-STUTTGART.MPG DOT DE> on 08/04/98
02:28:20 AM

        Please respond to "ADSM: Dist Stor Manager"
<ADSM-L AT VM.MARIST DOT EDU>

        To:   ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:  IBM RS6000 F50 4-way




        we are planning to move our ADSM server to an
        IBM RS6000 F50 4-way.
        Anybody have good or bad experiences with ADSM
        on this hardware ?
        --

------------------------------------------------------------------------
---
---
        ---
        ---
        Karl Roessmann                          Tel. +49-711-689-1657
        Max-Planck-Institute Stuttgart          Fax. +49-711-689-1632
        Heisenbergstr. 1
        70506 Stuttgart                         email
        roess AT dvfkf.mpi-stuttgart.mpg DOT de

------------------------------------------------------------------------
---
---
        ---
        ---