For what it's worth, in the *old* TSM 3.1, I have seen this when you =
have
done a
DELETE VOL on a primary stgpool volume, and/or when the primary tape is =
bad
(i.e, unavailable or destroyed), and some tapes in the backup stgp =
group are
bad
also.


Hopefully, it's something up with TSM 3.7, and not the above!



good luck!



Lisa Cabanas








John Sorensen <sorensen AT storsol DOT com> on 02/22/2000 06:20:19 PM

Please respond to sorensen AT storsol DOT com








 To:      ADSM-L AT VM.MARIST DOT EDU

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



 Subject: Re: Bitfile not found,              Invalid Object
          Header in Retrieve Operation on NT restore








At another site, we are seeing archive objects on an AIX TSM server =
running
3.7.1 with very much the same error.  The files were archived last =
week, and
attempts to retrieve 5 of them out of the total of 10 return the =
following
messages in the activity log:

ANR9999S bitfile not found for retrieval
ANR0540W retrieve or restore failed, data integrity error detected

As in Laura's case, the client gets the "object unavailable" error.  =
The
client (OpenVMS ABC) is based on the 2.1.5.0 API.

The customer was going to try an AUDIT DB but it'll have to wait till
overnight.

Is something up with 3.7.1?

John Sorensen
SSSI