Hi René,
with both the server and the client on 4.2 level, it seems that unicode
gets always used (at least with new nodes). That's fine as all problems
we had with national characters should be fixed now.
There's a problem with displaying the filespace names in dsmadmc (q
files resulted in "..." being displayed instead of the filespace name).
This problem is fixed in 4.2.1.8 and later.

When not using 4.2 on both server and client, I think the old rules for
USEUNICODE are still effective, but I haven't found much on this in
Tivoli documentation.

Best regards,
Michael
--
Michael Bartl, Dipl. Inform. (FH)           mailto:michael.bartl AT cw DOT com
Michael Bartl, Dipl. Inform. (FH)           mailto:michael.bartl AT cw DOT com
Backup Services, IT Germany/Austria         Tel: +49-89-92699-806
Cable & Wireless Deutschland GmbH.          Fax: +49-89-92699-302
Landsberger Str. 155, D-80687 Muenchen      http://www.cw.com/de


"Lambelet,Rene,VEVEY,GL-IS/CIS" wrote:
> 
> Hi,
> 
> we have directories with accented characters in our directories names and
> also in file names. What should be coded in the dsm.opt, using TSM client
> 4.2.1.20 for W2K and TSM server 4.2.1.7? Same question using TSM server
> 4.1.2.4 ?
> 
> Is it USEUNICODNAME YES or NO ? What are the main reasons for using YES or
> NO, sorry but doc is not so clear for me !
> 
> Thanks a lot for helping
> 
> >       René Lambelet
> >       Nestec S.A. / Central Support Center
> >       55, av. Nestlé  CH-1800 Vevey (Switzerland)
> >       *+41'21'924'35'43  7+41'21'924'28'88  * K4-117
> >       email rene.lambelet AT nestle DOT com
> >       Visit our site: http://www.nestle.com
> >
> >               This message is intended only for the use of the addressee
> > and
> >         may contain information that is privileged and confidential.
> >