a bug in 'comm', v5.2.1?

[j . frank]

Hello,
I used a (self written) script for intrusion detection, wich worked  
very well on my older machine (under Caldera Open Linux 2.3). Now I  
want to use it on my SuSE-PC and didn't get the correct logfile  
output. I found the reason in binary file comm's variation of function  
between the versions 1.2.2 (on Caldera) and 5.2.1,  wich came with  
SuSE 9.2.
See the attachments commf1f2.xxx; they both were generated as an output of
"comm -3 f0 f1" with the different binary's versions. I need the  
output like it is in 'commf1f2.122'.
Is there a solution (or work around) for my problem?
Thanks and greetings
Juergen Frank

commf0f1.521
Description: Text document

commf0f1.122
Description: Text document

f0
Description: Text document

f1
Description: Text document