I am afraid you might have an unsupported configuration.
Looking to ITSM v5.2 Administrator's Guide, Chapter 5 "Configuring Storage
Devices", section "Mixing Device Types in Libraries":
"While the Tivoli Storage Manager server now allows mixed device types in
a library, the mixing of different generations of the same type of drive
is still not supported.
...
Mixing generations of the same type of drive and media technology is
generally not supported in a Tivoli Storage Manager library.
...
If you need to transition from an older generation to a newer generation
of media technology, consider the following guidelines:
- Upgrade all drives in a library to the new generation of media
technology."

For me the problem is that both "def dev" statements are using same
devtype=dlt!!! Thus the server does not distinguish between drives. If you
look in the example, it is not with DLT+SDLT but with DLT+LTO, and
difference is made by devtype parameter of the drives.

--> IBM said that the mixed drives are supported in the same library.

But not all mixtures are supported. So either you or IBM had to check will
be your configuration supported or not!
Hope I am wrong.

Zlatko Krastev
IT Consultant






Kurt Beyers <kurt.beyers AT PANDORA DOT BE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
06.11.2003 20:54
Please respond to "ADSM: Dist Stor Manager"


        To:     ADSM-L AT VM.MARIST DOT EDU
        cc:
        Subject:        device class mount point mixed library (DLT7000 and 
SDLT320)


Hello,

I've posted a question a few weeks ago about DLT7000 drives and SDLT320
drives in the same library (Storagetek L180). IBM said that the mixed
drives are supported in the same library. The TSM server is 5.2.1.2 on
Windows2000.

I've defined today the library as follows:

define library mixlib libtype=scsi
define path server01 mixlib srctype=server desttype=library
device=lb3.0.0.0

define drive mixlib dlt_mt4
define drive mixlib sdlt_mt5
define path server01 dlt_mt4 srctype=server desttype=drive library=mixlib
device=mt4.0.0.0
define path server01 sdlt_mt5 srctype=server desttype=drive library=mixlib
device=mt5.0.0.0
define devclass dlt_class devtype=dlt format=dlt35c library=mixlib
define devclass sdlt_class devtype=dlt format=sdlt320c library=mixlib
define stgpool dlt_pool dlt_class maxscratch=20 (was already defined of
course)
define stgpool sdlt_pool sdlt_class maxscratch=20


The first serie of tests went fine: labelling of SDLT tapes
                                               backup of the TSM database
to a DLT7000 tape

I started then the migration from the primary DLT volumes to the SDLT
primary pool. This confuses me from time to time. The following sitations
happened:

1. SDLT volume mounted in SDLT drive and a bit later the move failed with
the warning ANR1145W (not enough mount points available). All drives and
paths were online A 'query mount' didn't give any other mount requests.

2. SDLT volume mounted in SDLT drive, DLT tape in the other SDLT drive and
the 'move data'  is successfull.

3. SDLT volume in SDLT drive and DLT tape in DLT7000 drive (that is what I
would expect). The'move data' is successfull.

If a new 'move data'  is started, you typically see the message 'waiting
for a mount point in device class sdlt_class or dlt_class. But how does
TSM knows which drive belongs to which device class? Where is this link
defined (through the format:dlt35c / sdlt320c in the device class?)? Can
you check which drives belongs to a specific device class according to
TSM?

And why is a DLT tape mounted in a SDLT drive if the DLT drive is ready to
be used as well?

Any input that will make this more clear to me how TSM chooses a drive is
more then welcome. Thanks in advance,

Kurt