Hello,
IC21749 is fixed in version 3.1.0.6, which is available as of this
morning.
The problem with "wrong" filenames and directories not expiring
(APAR IC21764) is still out-standing. This problem will occur for
nodes backed up with ADSM clients previous to 3.1.0.5, but new
nodes using 3.1.0.6 should not see this problem. Files and
directories with umlauts or other international characters are now
properly handled, as of 3.1.0.5L and 3.1.0.6, except for IC21764,
as stated above.
We are working on a special version of the ADSM command-line client
to clean up the IC21764 problem. I had hoped to release it some time
early or mid-November, but at the last minute we discovered a case
that we were still not cleaning up. Rather than release a clean-up
utility that works 95%, we are waiting until it is working 100%.
Hopefully this will occur before the end of December.
My recommendation is to apply 3.1.0.6 and not go back to 3.1.0.3.
While the files-not-expiring problem is annoying, new backup
versions created with 3.1.0.6 will be properly displayed and
handled by ADSM, both in the command line interface and GUI. Once
the clean-up utility is available, you will need to use it on a
one-time-only basis to clean up the files-not-expiring problem.
Best regards,
Andy
Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."
Gerhard Rentschler wrote:
>
> .....
>
> I checked the databases and found APAR IC21749 which exactly describes
> the problem. The recommendation in the APAR is to use a different
> language.
> Now I have the following questions.
> 1. With 3.1.0.3 I had problems with the US English version and
> Filenames with National characters (e.g. umlauts). They were not
> dislayed correctly. Has this been fixed in 3.1.0.5? Sorry, I had
> problems to understand the recent discussion on this subject.
3.1.0.5L does not fix the "Assertion failed!" problem. You cannot use
the German version.
The problem with National characters in file/directory names is another
one. It has been fixed, but the "wrong" files/directories will never
expire.
> 2. Why doesn't this problem occur on each system where the client is
> installed?
???
> 3. What should I recommend to the user? Going back to 3.1.0.3?
Is it possible to mix an existing 3.1.0.5-UNC-oriented backup with a
pre-3.1.0.5 ?
> Best regards
> Gerhard
> ---
> Gerhard Rentschler email:g.rentschler AT rus.uni-stuttgart DOT de
> Regional Computing Center tel. ++49/711/685 5806
> University of Stuttgart fax: ++49/711/682357
> Allmandring 30a
> D 70550
> Stuttgart
> Germany
Best regards
Gerhard
---------------------------------------- gerhard.ginzler AT akh-wien.ac DOT at
Institut f. Medizinische Computerwissenschaften (IMC) (+43)(1)40400-3633
Institut f. Medizinische Computerwissenschaften (IMC) (+43)(1)40400-3633
Universitaet Wien / Allgemeines Krankenhaus Fax: (+43)(1)4088188
Waehringer Guertel 18-20
A-1090 WIEN
|
