>use this command to determine if your filespace is unicode enabled:
...
>If unicode is NO you have to rename your existing filespace and have to backup
>the node again (new full backup).
>Then it should be unicode enabled.

Joachim - The original posting was from a Linux client user...

TSM supports Unicode only for the Windows and Macintosh environments.
The Linux system is pretending to be Windows for the purpose of serving
Windows Shares, as a file server.  But as a full-service server it also
somehow needs to back up those files.  The only way I see to accommodate
that is code page handling through Samba, per my prior posting.

   Richard Sims, BU