I see these almost daily on one of my servers.

I happened to have an open ticket/conversation with an IBM TSM L2 person
and asked him about this. His reply was:

I did a quick search on the ANR1330E and ANR1331E message and found APAR
IC50141 and some knowledge items (1214031). The APAR was closed as FIN and
stated to be "The server code will be modified in a future release to
solve this problem." You might want to look at the AUDIT VOLUME command
and see if that resolves the issue. If not, please open a new PMR to have
this issue addressed.




"Gill, Geoffrey L." <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[email protected]>
01/23/2007 02:35 PM
Please respond to
"ADSM: Dist Stor Manager" <[email protected]>


To
[email protected]
cc

Subject
[ADSM-L] never before seen message






This is the first time I have seen anything like this and I thought I'd
throw it out there to see if anyone else has. There is nothing in the
AIX logs to indicate anything odd going on there. It looks like there
was a migration running, which reports SUCCESS, when this happened and I
see no tape error messages and no tapes in an odd state.



TSM Server is AIX 5.3

TSM is 5.3.3.0




1/23/2007 6:45:43 AM ANR1330E The server has detected possible
corruption in an object being restored or moved. The actual values for
the incorrect frame are: magic 5A4D4E50 hdr version 0000 hdr length 0005
sequence number 00000009 data length 00329C3F server id 00262096 segment
id 0000000000000000 crc 00000000.


1/23/2007 6:45:43 AM ANR1331E Invalid frame detected. Expected magic
53454652 sequence number 00000980 server id 00000000 segment id
0000000188983073.







Geoff Gill
TSM Administrator
PeopleSoft Sr. Systems Administrator
SAIC M/S-G1b
(858)826-4062
Email: [EMAIL PROTECTED]

Reply via email to