The problem is not in the server. I had PMR open on this and the answer
was - it would be fixed in 4.2.2 client (not server). The problem is
client displays wrong data not server returning wrong values.
So whatever is the server - we have to wait for 4.2.2 client. Have anyone
tested it with v5.1 client?

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        Re: 4.2.2.0 Problems

> Noticed two minor problems:
> 1) The query process of a Move Data command always shows (erroneously) a
> very large number of "Unreadable Bytes".
[Other minor problem deleted]

I have seen the same problem with a 4.2.1.9 server under OS/390. This
seems
to be part of a large genre of errors in calculated numbers in messages
and query responses. Some of these errors are so obvious that I am
starting
to wonder whether the developers make any effort at all to test this sort
of thing before shipping new releases.