Hi Wanda,

This sounds like one for support.
I don't know what your server version is, but is at a level which supports the
command
SET CONTEXTMESSAGING ON
This is supposed to give you a bit more background detail to the ANR9999D






"Prather, Wanda" <Wanda.Prather AT JHUAPL DOT EDU> on 11/13/2001 10:30:22 PM

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

To:   ADSM-L AT VM.MARIST DOT EDU
cc:    (bcc: John Naylor/HAV/SSE)
Subject:  Re: Antwort: Re: ANR9999D with a strange message



Yep.  I've done audit on EVERY volume in the library.  More than once.

Also, since the primary pool is collocated and the offsite pool is not, it
is frequently impossible to tell WHICH primary volume needs to be restored.

You see the error on the reclaim of the copy pool tapes; since we normally
hit many tapes in a reclaim cycle, you find these errors in the log and
can't really tell which primary pool tape is the culprit.

And when I can tell, the RESTORE VOLUME doesn't always fix it, and I end up
deleting the remainin few files on teh copy pool tape, on the assumption
that TSM will pick them up again the next time a do BACKUP STGPOOL.

So far, I"m baffled.

I see maybe 50 files a week with this error, while millions have gone
through reclaim.  And it's only the copy pool tapes that seem to have a
problem, so I haven't been scared enough by it yet to shut down and audit
the DB.  I"m thinking of doing that over the New Year holiday.