From: ADSM: Dist Stor Manager on behalf of Schneider, John Thanks for everybody who responded, but when you reply to a post on this list, please try to make sure you know what you are talking about. Of the 5 responses I got, 4 of them made no sense. Like the guy who recommended I upgrade to TSM 5.1.9, when I stated I was running TSM 5.2.7.1 already.
...which all goes toward what I used to say in the TSM FAQ: post and read for awhile, and you'll learn whose answers are generally worth listening to, and whose aren't. Something in the library is not keeping TSM abreast of scratch status. Upgrading probably won't fix the issue in that case; checking firmware levels on the library is more likely to fix it. Try running CHECKOUT LIBV to remove the scratch tapes, and then run CHECKIN LIBV on those volumes. Does that fix it permanently? Temporarily? -- Mark Stapleton ([EMAIL PROTECTED]) Senior consultant
