Hello,

Please note that this post applies only to those Win32
clients that meet ALL of the following qualifications:

1) The client has international characters (i.e umlauts,
   accents, etc.) in their file names.

2) The client has or had the version 3.1.0.3 (or below)
   ADSM client code installed on it.

3) The client used USEUNICODEFILENAMES NO.

We have done some additional testing since my post from
yesterday, and I have some additional information on
problems with the 3.1.0.5 client and international
characters in file names.

If the system has client version 3.1.0.3 on it and you
apply version 3.1.0.5 (or the fixtest for 3.1.0.5) then
the first time incremental backup runs, files with
international characters in their file names will be
backed up, even if they have not changed. This is to be
expected, as we have corrected problems with how the
files were stored on the ADSM server with version 3.1.0.3
or below.

It is also expected that the prior version of these
international files will be expired. However, this is
not happening.

Therefore, if this post applies to you per the above
qualifications, then I do not recommend applying either
the formal PTF version 3.1.0.5 or the fixtest for 3.1.0.5
until we resolve this problem with the older files not
expiring. NOTE: This is not the same problem as IC21764.

Once we have resolved the problem (hopefully in a few
days), a new fixtest will be built.

Thank you,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com

Hello,

We are running L03 on our production NT Clients. I've experienced the
international chars problem on a L05 NT test machine.
Question: If we are going from L03 to L05L with putting USEUNICODEFILENAM=
ES
OFF (language ameng), shall we experience the problem that all files/dirs
with international chars will be backuped again?
This may cause ou big DB (45GB) on MVS to explode!

Francis.