Hello,
I discovered the following problem with an updated
TSM 4.2.x to TSM 5.1.x client (Server TSM 4.2.2.x).

This post is only to inform you.


 APAR= IC33548  SER=                            IN INCORROUT
 TSM 5.1 UNIX CLIENT BACKUP AGAINST EXISTING 4.2 OR BELOW DATA
 MAY RESULT IN UPPER TO LOWER CASE CHANGES IN OBJECT NAMES


ERROR DESCRIPTION:
The TSM V5.1 UNIX backup/archive client may, under some
circumstances, not preserve case sensitivity in queries
of object names. Names are backed up correctly. The external
symptoms are presented through the messages ANS1228E and
ANS1304W during backup processing. The backup process will
actually be trying to expire the object as such an object does
not exist on the client machine, but the expire will always
fail. The following are the full text of the
messages received during a backup when this problem exists:
Expiring-->            512 /usr/iMNSearch/lib ¬Sent|
Directory-->           512 /usr/IMNSearch/lib ¬Sent|
Retry # 1  Expiring--> 512 /usr/iMNSearch/lib  * Unsuccessful *
ANS1228E Sending of object '/usr/iMNSearch/lib' failed
ANS1304W Active object not found
Retry # 1  Directory--> 512 /usr/IMNSearch/lib ¬Sent|
ANS1802E Incremental backup of '/usr' finished with 1 failure

 As seen in the above messages, the backup client has
 identified the need to expire an object by the name of
 /usr/iMNSearch/lib. However an object of this name never
 existed. The change in case, from upper to lower during
 client processing has caused the client to believe there
 is a unique object by this uniquely cased name. There is
 not. All information stored on the server is correctly
 cased. This issue does cause an extra copy of the object
 to be backed up.



 LOCAL FIX:


Bye
  Rainer Tammer