"Kelly J. Lipp" wrote:
>
> This is a reprise of a thread started in December.
>
> Flame on:
>
> HAS ANYONE MADE THIS WORK WITH TSM 4.1???????
>
> Flame off.
>
> The documentation is not clear: Does ADSMSCSI support this baby or do we
> need to use the device drivers shipped with the library?  The library
> documentation suggests that if you are going to use TSM you should not use
> the drivers shipped with the library.  If, on the other hand, you simply
> start the TSM device driver, one can't see the drives.
>
> Could anyone that has made this work please document here what you did?

This may be kinda late to respond, but here's what I discovered:

At this time you have to use the Windows RSM stuff to get the library to
talk to the outside world--labelling, checkin, checkout, etc. There is
doubtless some way to script the interaction, much like we use shell
scripting to control TSM running under *NIX, but I had a customer
standing next to the server, tapping his foot and waiting, and Microsoft
is not exactly forthcoming with details on controlling RSM libraries.

We ended up stepping back to NT 4, which itself turned out not be a
trivial exercise with the new Ultrium library. The secret turned out to
be this:

1. If you're using low-voltage SCSI adapters, as my customer's Compaq
server uses, you're going to have a hard time getting a library with
numerous drives to configure properly. The NT Tape Library applet in
Control Panel will probably detect the drives but not the changer.
Supposedly this has to do with the SCSI buffer size. The trick seems to
be to initially configure the library with only the changer and one
drive; after you accomplish this, you can add on the rest of the drives
and add them.

2. The trick to setting up the drivers for the library and the drivers
is to follow the directions in the PDF file in the Ultrium driver cd
EXACTLY. Don't try to intuit the driver installer process; this is
*definitely* a case of RTFM.

The ADSMSCSI driver is not operational with Win2K as of this time. The
rumor is that Tivoli development is trying to modify it to work, but
there is no timetable or promises at this time.

--
Mark Stapleton (stapleto AT berbee DOT com)
Mark Stapleton (stapleto AT berbee DOT com)