Thanks, Larry

But, unfortunately, it's not that sinple-- the microcode is current.  So, I
don't have anything to pursue down that avenue......







Larry Way <Larry.Way AT TRW DOT COM> on 02/28/2000 11:48:56 AM

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








 To:      ADSM-L AT VM.MARIST DOT EDU

 cc:      (bcc: Lisa Cabanas/SC/MODOT)



 Subject: Re: sql select statement for error state?: yes &/or
          for writeand              read errors on tape vols?








You need to make sure you're on the lastest microcode for your 3570 drives.
There were some reported problems about bad microcode...I've experienced same
problems with i/o errors and vcr data repair.  Problems went away after last
microcode update.  I had experienced this problem for a solid month on a daily
basis...

Good Luck

Larry

Larry Way
SL09/100D
408-743-4242  voice
408-743-4201  fax

>>> CABANL AT MAIL.MODOT.STATE.MO DOT US 02/28/00 08:38AM >>>
Has anyone already written a dsmadmc sql select query for "bad" tapes??  If so,
would you *please* share?

Also, out of curiosity, how do ya'll handle your tapes' life cycle?  I have 10
locations with 3575 libraries, B model drives,  using the Magstar MP tapes.
Have you written scripts to keep track of usage, and to determine when to
"sunset" some of the harder working tapes?  Does anyone *really* take IBM at
it's word on the 10-year usability on the tapes?  Our systems are three yrs old
now, with the vast majority of tapes being that old also.  I have noticed a
trend of increasing i/o errors, repairing VCR data, and read/write errors.  The
CE's keep giving the drives a clean bill of health, but the bottom line is: I
have been loosing data!

The voices of those more experienced in the ways of proper tape media management
(vague Monty Pyton reference) are encouraged to apply!

thanks !
Lisa