One of our Windows administrators has been attempting a cross-system
restore using the -virtualnodename option. The system that backed up the
files was a Windows NT system with 5.1.7.0 client code. The system
attempting to restore the files is a Windows 2003 system with 5.3.4.3
client code. The TSM server is a mainframe Linux system with 5.3.4.0 server
code. The restore restores about seven gigabytes before failing. The last
part of the error log is as follows:

01/08/2007 15:10:06 ANS1946W File
\\fa001new\e$\Home\jpc101\FY_2002\RADIOL~1.XLS exists, skipping
01/08/2007 15:10:09 ANS1946W File
\\fa001new\e$\Home\jpc101\FY_2002\SURVEY~1.XLS exists, skipping
01/08/2007 15:13:14 The 30472th code was found to be out of sequence.
The code (4025) was greater than (3839), the next available slot in the
string table.
01/08/2007 15:13:14 ANS4039E Error processing
'\\fa001new\e$\Home\yxl103\mcare\healthpartners03(a).xls': compressed file
is corrupted and cannot be expanded.
01/08/2007 15:13:14 The 12982th code was found to be out of sequence.
The code (1771) was greater than (1714), the next available slot in the
string table.
01/08/2007 15:13:14 ANS4039E Error processing
'\\fa001new\e$\Home\yxl103\mcare\HPCAL02.xls': compressed file is corrupted
and cannot be expanded.
01/08/2007 15:13:23 HlClose(): Win32 RC 1336 occured restoring NTFS
Security Attributes on object
'E:\Home\yxl103\PO.BOX\MISCFILES\FOXPRO\UVARA20.DBF'.
01/08/2007 15:13:23 HlClose(): Default NTFS Security Attributes have been
set.
01/08/2007 15:13:25 Return code 260 unknown
01/08/2007 15:13:25 Unknown system error
Please check the TSM Error Log for any additional information

The ANS1946W messages shown are the last two of a much larger number
of such messages. It would appear that original client had a lot of
files with long names imitating the style of the short names generated
by Windows.

The TSM messages manual was not particularly helpful, since the TSM
developers did not see fit to attach message identifiers to most of
the messages shown above. Web searches for various text strings in
the messages have so far not turned up anything particularly helpful.
Does anyone have any suggestions for trouble-shooting this problem?