Thanks to all who replied.
It turns out that the record size of the stream file was the culprit,
somehow it had been built at 160 bytes. What drove me crazy was that this
job had been in production for months without any problems (However it was
the first time that the processed data caused the 'sort' path to be taken).
Regards
Paul H. Christidis