Comments on: Generated code differences in COBOL

By: GeneInAK

GeneInAK — Wed, 04 Jan 2006 12:35:05 +0000

As mentioned by another previously, you could try declaring a variable of the same type as FieldA Pic S9(3) value +0. Notice the sign of 0 is positive, the sign bit could be your problem.

By: LeahDawn

LeahDawn — Wed, 04 Jan 2006 09:39:08 +0000

I’m not familiar with Endevor, but, it appears that when the assembler code is generated for the Endevor, it is designed to treat a blank in the numeric field as a zero to surpress abends and does a character compare. Where as the other version uses a compare packed to do so. This could explain why we have abends in our software that others do not when fields aren’t initialized to zero.

By: fskovacs

fskovacs — Tue, 03 Jan 2006 08:42:41 +0000

As it were, for the NUMPROC option, the default value where I am (MIG) is different from what is provided by IBM (NOPFD). What MIG does is force all numeric compares to be decimal compares as opposed to logical compares.

Thanks for your help

By: mrmullins

mrmullins — Fri, 30 Dec 2005 17:00:15 +0000

It has to be either a compiler option, or a difference in the field definition. Check SYSLIB concatenations between Endeavor and non-Endeavor.

Kind regards,
Ray Mullins