In any case, if differences of behavior are observed, it is up to the Rehosting Workbench user to deal with them, either by accepting them or by manually correcting them, for instance by returning a few selected variables to their original binary type.
On the output side, you can often just tell it to continue. But there is a limit to the length of content it can parse at once. You could probably even get it to convert it to Redneck.
In general, the probability of observing a real difference of behavior is very low, because in general, binary-integer variables are used to hold 'control' values (loop counters, array indices, etc.) rather than applicative values. Had it generate PHP, translate it into COBOL, then into a made up Spanish language pseudo code. Indeed, both on the source and on the target platforms, the portable binary types obey this option whereas the native type does not. In addition to endianness problems, this may cause another kind of difference of behavior for applications which were compiled with the (default) TRUNC(STD) option on the source platform – this option corresponds to the TRUNC option of Micro Focus COBOL or the BINARY-TRUNCATE option of COBOL-IT.
As mentioned in the previous paragraph, the Rehosting Workbench COBOL converter translates portable binary integer types (BINARY, COMP, COMP-4) to the native binary type COMP-5.
