Werner,
the problem came with V3.1.0.3 (PTF3) of the NT Client. When one of those
special characters came up, the Client ran into an error and skipped the
rest of the filespace.
In NT-Explorer you can see the characters as small vertical blocks, from the
commandline they show as questionmarks.

This special problem is fixed in PTF5/6, we use V3.1.0.6Q at the moment.
When you have german umlauts in your filespaces, you can expect to get LOTS
of errors in the dsmsched.log after upgrading to PTF6 (we got 30000+ on some
servers, each night).

Andy Raibeck wrote a small but great tool to fix those errors. Just remember
this tool when "active object not found" errors occur. You'll then find it
in
ftp://index.storsys.ibm.com/adsm/fixtest/v3r1/win32/intel/
(look for IC21764L2)

Good Luck,
regards, Michael