Can you use relabelonscratch to force a relabel of each volume as it
goes scratch?  The new label should be in the higher density and from
that point onward you should get the benefit of the new drives.

Regards

Steve.

Steven Harris
TSM Admin
Paraparaumu, New Zealand

On 6/11/2010 4:58 AM, Matthias Feyerabend wrote:

 There is no mixture of drives in our library nor is there a mixture
of generations of 3592 media.
There are only IBM3592-E06 (TS1130) and only long JB media.
Data is written in different forms, E05 and E06 alike.
There are no production problems arising from this configuration, only
question is how to use most of it.
I bet there is some way to tell if it is efmt3 or efmt2 a given tape
is written with, perhaps  using tapeutil.

Matthias Feyerabend

Am 11/5/10 3:25 PM, schrieb Richard Sims:

Observe the TSM documentation, which says:
"Avoid specifying DRIVE when a mixture of drives is used within the
same library."
and
"For optimal performance, do not mix generations of 3592 media in a
single library. Media problems can result when different drive
generations are mixed."

There is backward compatibility to E05 from E06. The new drives can
read and write the old tapes.

Yes, but you are seeking to achieve specific results, where only
specific definitions will guarantee such results.  Loose definitions
can make for undesirable results, and problems.  You are already
having problems telling the tapes apart.

    Richard Sims

On Nov 5, 2010, at 10:16 AM, Matthias Feyerabend wrote:

I am using format=drive in my devclass, no problem reading E05
tapes. A filling E05 tape will be written in E05 format, a new one
in E06 format.
But how to see which tape is written in E05 ? ( the written capacity
is some hint, but on filling its difficult).

Am 11/5/10 2:51 PM, schrieb Richard Sims:

Would not your prior use of 3592-E05 have been with devclass Format
3592-2, and new use of 3592-E06 be with devclass Format 3592-3, in
a recent TSM version/level supporting that specification?

     Richard Sims