If you look at the results of "q proc f=d" or "q se ### f=d", you might come close to knowing how much has transpired -- but you need something (like ServerGraph?) to track progress so you can see what the instantaneous performance level of a given task... kinda like vmtune/vmstat every 5 sec's, then compare the delta and run a continuing, smooth curve graph connecting the dots across the intervals.
I agree with Mark's post; while this is "nice to have", and there IS more instrumentation being incorporated in latest versions, I would put the recent rash of relentless, recurring, regression bugs at the very HIGHEST priority -- new features aren't worth the effort when they come at the expense of serious breakage (eg, the recent/ongoing saga with expiration & conflict-lock!). Don France Technical Architect -- Tivoli Certified Consultant San Jose, Ca (408) 257-3037 mailto:[EMAIL PROTECTED] Professional Association of Contract Employees (P.A.C.E. -- www.pacepros.com) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Zlatko Krastev Sent: Thursday, June 27, 2002 7:28 AM To: [EMAIL PROTECTED] Subject: Re: Shortfalls in tsm/adsm 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" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] 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 enjoy every minute of it... | | http://www.travellingkiwi.com/ |
