I cannot answer to the question but am afraid the answer is negative.
You can even find an APAR caused by TSM-driver for AIX (!!! not Solaris or
HP-UX) not being written according to AIX rules. Result: the devices being
deleted/unconfigured after restart (I learned this the hard way).
So lets not laugh too much on the others but try to be *always* better
than them.

Zlatko Krastev
IT Consultant




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

Subject:        Shortfalls in tsm/adsm

Hi.

reading a recent post on why people love tsm vs networker brought back a
lot of memories. Most of the great, but one that I just can't forgive.
There STILL appears (6 years after I broached the subject with the adsm
developers) to be no way to monitor in real-time what each of the tape
drives in the library is actually doing...

For example on Networker (And I know it's awful, I hate it as much as
the next geek who isn't enamoured by fancy GUI's etc) you can see
exactly what each drive is doing, AND HOW FAST IT'S DOING IT! Writing at
3.5MB/sec! Great. It's working fine. On tsm? Well there's manual mental
arithmetic and query proc if you feel brave...

Any chance I'm mistaken & the developers have actually fixed this
shortfall? Or at leats implemented a kernel table in their device
drivers so you can see the device stats like you can for hdisks?

TIA

Hamish.

--
I don't suffer from Insanity...         | Linux User #16396
I don't suffer from Insanity...         | Linux User #16396
        I enjoy every minute of it...   |
                                        |
http://www.travellingkiwi.com/          |