I also experienced this problem, and besides doing everything that Reinhard
says, I also had to update the devclass for the 3590's to FORMAT=3590E-C instead
of DRIVE.   That was the ultimate solution.

In our case this problem quickly came to light because restores began to fail.
The odd thing about all this is that our drives never were B drives.  They have
always been E drives but were converted to extended capacity about 2 weeks
before the errors began to appear  'out of the blue'.  By that I mean everything
was working fine and then all at once at 19:38 the errors began to show.  Never
figured out why.  The TSM server had been up for months, no microcode changes on
the drives, no ATL reboot, no Atape or atldd driver software changes, nothing,
just 'time for errors' (computers, got to love them).  Also this has only
affected my 3.7 servers, the 3.1 servers continue to function fine, despite have
been through B to E to Ex conversions.

Al Barth
Scudder Kemper Investments



|--------+------------------------>
|        |          Reinhard      |
|        |          Mersch        |
|        |          <mersch@UNI-MU|
|        |          ENSTER.DE>    |
|        |          Sent by:      |
|        |          "ADSM: Dist   |
|        |          Stor Manager" |
|        |          <ADSM-L AT VM DOT MAR|
|        |          IST.EDU>      |
|        |                        |
|        |                        |
|        |          09/27/00 01:59|
|        |          AM            |
|        |          Please respond|
|        |          to "ADSM: Dist|
|        |          Stor Manager" |
|        |                        |
|--------+------------------------>
  >----------------------------------------------------------------------------|
  |                                                                            |
  |       To:     ADSM-L AT VM.MARIST DOT EDU                                   
      |
  |       cc:                                                                  |
  |       Subject:     Re: Changing configuration to use 4 drives              |
  >----------------------------------------------------------------------------|



Ken,

delete the upgraded drives and define them again. Set access to all tapes
in FILLING state to READONLY.

Background: ADSM internally keeps record of all drives and tapes of beeing
of type B or E. ADSM still thinks, that the old drives are of type B, until
you redefine them. It will not mount a type E tape on a type B drive. It
will also not mount a type B tape on a type E drive for writing, therefore
the FILLING tapes should be set READONLY until they are empty.

Ken Chamberlain writes:
 > We've just upgraded our 2 3590 B drives to 3590 E drives and added 2 new E
 > drives.
 > The new drives are available according to "lsdev -C".  The new drives have
 > been defined to ADSM via "define drive"  and set to "online=yes".  We've
 > upped the mountpoints parameter of the 3590 devclass to 4.  But when we try
 > to use all 4 drives simultaneously we get ANR8447E
 > "No drives are currently available in library <our library name>" and mounts
 > fail after the first two mounts.
 >
 > Somewhere I've missed configuration to allow 4 drives to be used
 > simultaneously.  Any ideas?
 >
 >
 > Ken Chamberlain
 > University of Toronto
 > Phone:(416) 978-1582
 > Fax:  (416) 971-2085
 > E-mail: ken.chamberlain AT utoronto DOT ca

--
Reinhard Mersch                        Westfaelische Wilhelms-Universitaet
Reinhard Mersch                        Westfaelische Wilhelms-Universitaet
Zentrum fuer Informationsverarbeitung - ehemals Universitaetsrechenzentrum
Roentgenstrasse 9-13, D-48149 Muenster, Germany      Tel: +49(251)83-31583
E-Mail: mersch AT uni-muenster DOT de                       Fax: 
+49(251)83-31653