For the user that has hit the problem now, all I know is that it is some
form of Linux system running under VMware. Further information provided over
the weekend says that the problem only happens in an SSH connection and only
inside QM, not at the shell command prompt. This tends to suggest that it is
in some way connected with the specific API used to read the data (the
read() function in this case).

I have personally seen this with UV on a VMware system in the past. What I
am looking for is some suggestion of why it happens.

Thanks.