Even with 3.1.0.6 with USEUNICODEFILENAMES  NO (as specified in README.TXT)
does
 not solve the problem. It's why I mentionned the special utility IBM is
writing.
I don't know why, in some cases, it solves the problem, why in other cases,
it doesn't.


-----Message d'origine-----
De : Werner Nussbaumer <W.Nussbaumer AT datacomm DOT ch>
De : Werner Nussbaumer <W.Nussbaumer AT datacomm DOT ch>
À : ADSM-L AT VM.MARIST DOT EDU <ADSM-L AT VM.MARIST DOT EDU>
Date : mercredi 16 décembre 1998 11:49
Objet : Re: 'ANS1304W Active object not found' errors


Pascal Destouches wrote:
>
> Hello,
>
> This problem occurred when you migrate from a V2 client to a v3.1.0.5 (or
> 3.1.0.6) client and when you have international characters in filenames or
> directories (you should have some ... it seems to me to be spanish names).
>
> IBM is currently writing a special utility which should fix this problem.

With the newest ADSM client software I did no more have this problem (it
has to do with special international characters like "äàöé". This was
APAR IC21764. Important is that the following option is set:

USEUNICODEFILENAMES OFF

Regards
Werner Nussbaumer