sign bit representation during natural to cobol conversion

sandy_venkat · New User Joined: 16 May 2007 Posts: 35 Location: India

Hi,

I converted a Natural program to cobol. I am facing a situation here. The dataset length if 400.

In the 359th bit and one other bit, i am getting a F(hexa decimal value for positive) when i generate the dataset by running the natural program while i am getting a C(another hex representation for +ve) using the cobol program.

While converting from Natural to cobol do we face situations like these? Are these a problem. If so how can it be solved?

Thanks,

Sandy

ofer71 · Posted: Wed Jan 02, 2008 12:07 pm

We faced that issue during NATURAL to COBOL conversion.

Since we did it using our automatic tool, we conducted the following strategy regarding the issue:
1. We removed the S from any converted COBOL variable that didn't need it (like dates, timstamps etc.).
2. When reading data that was created by NATURAL, we used a special routine that converts the F to C before processing the data.

O.