We backup OS/2 Clients with ADSM V2R1M8 to TSM 5.2.2.0 Server. I know it's
not a supported configuration, but it was working up to TSM 5.2.1.3.

Since upgrading to TSM 5.2.2.0 we get the following message when restoring
files in dsmerror.log

    02/24/2004 10:06:21  fileio.c  (3016): fioWrite: Unknown structured
data type, file: 'C:\ibmlxres.dll'
    02/24/2004 10:06:21  ANS4081S *** Unknown system error 150; program
ending ***

Switching on the traceflags we find:

    02/24/2004 09:40:20.0420 : os2filio.c(1185): HlOpen: Opening
C:\ibmlxres.dll' for Writing (NO OVERWRITE)
    02/24/2004 09:40:20.0440 : os2filio.c(1290): HlOpen:    file
successfully opened: seqNum: 0
    RestoreFile: Expanding file while restoring

    cmInitExpand: Initializing expander with maxBits: 13
    cmExpandData: Starting. inLen: 7 outLen: 32768
    cmExpandData: Starting expansion of 12 bit data
    cmExpandData: Starting. inLen: 16124 outLen: 32768
-->  RestoreFile: Assumed compressed file not compressed
-->  Restoring file data without expanding this shouldn't happen
-->  any more!!!
-->  02/24/2004 09:40:20.0530 : fileio.c  (2993): fioWrite(): File
'C:\ibmlxres.dll': Obtained Data Main Header
-->     SDB Version = '90'
-->  02/24/2004 09:40:20.0540 : fileio.c  (3016): fioWrite: Unknown
structured data type, file: 'C:\ibmlxres.dll'
    RestoreFile: Got a rc: 150
    02/24/2004 09:40:20.0600 : os2filio.c(1465): FileOpen: Opening
'C:\ibmlxres.dll'
    02/24/2004 09:40:20.0600 : os2filio.c(1486): FileOpen:    file
successfully opened: seqNum: 0.0
    02/24/2004 09:40:20.0600 : os2filio.c(1718): FileClose: Closing
seqNum: 0.0, filePtr=0
-->  02/24/2004 09:40:20.0600 : os2filio.c(1769): FileClose: truncated
'C:\ibmlxres.dll' from size:31040 to size:44018040
31040 Byte is the right size!
    02/24/2004 09:40:20.0600 : os2filio.c(1323): HlClose: Closing seqNum: 0
    02/24/2004 09:40:20.0600 : os2filio.c(1808): fioDelete: Deleting
file 'C:\ibmlxres.dll'
    02/24/2004 09:40:20.0610 : os2filio.c(4154): GetAclInfo:
NetAccessGetInfo rc=2222, aclSize=0 aclcrc=0.

The error is reproducable (deleting the filespace and making a new backup
and it always happens with the same files)
One workaround is not to use compression, the other is to restore with ADSM
Client V3R1M7.

With TSM 5.2.1.3 Server backup and restores are ok.

In this mailinglist I saw some mails regarding this problem with TSM Server
4.1.3.0 and  TSM Client 4.1.2.12 and earlier versions.
Did something find it's way back into 5.2.2.0?

Another problem is to go back to server version 5.2.1.3. Looks like the
database has changed and there is no way back.
When we install the older software and start the server with the original
database we get a message that it expected 48 columnes in table nodes but
got 50 and the server stops  working.
Anybody has an idea how it could be done?


Sincerely

Gerhard Hansmair