Incorrect reading of data in binary field in ebcdic file
Posted: Tue May 05, 2009 5:06 am
I am testing a job which we are moving from version 7.5 to version 8 of datastage.
I am finding a difference in the values read by datastage for a particular field in an ebcdic file. I am testing using the same file for the 7.5 and 8 versions of the jobs.
The version 8 is unchanged from the version 7.5 ( i.e it was exported from 7.5 and imported into 8 ).
When I view the input file using VEdit, I can see the hex value of the 1st field is:
00 00 00 02
This field is defined in datastage a binary 9 signed, usage COMP.
i.e. PIC S9(9) COMP.
In my 7.5 job, this field is read with a value of 2.
In my 8 job , this field is read with a value of 8590127600
Any ideas?
Is this a bug, or has the move to version 8 exposed some incorrect settings in the filestage in my job?
Thanks.
I am finding a difference in the values read by datastage for a particular field in an ebcdic file. I am testing using the same file for the 7.5 and 8 versions of the jobs.
The version 8 is unchanged from the version 7.5 ( i.e it was exported from 7.5 and imported into 8 ).
When I view the input file using VEdit, I can see the hex value of the 1st field is:
00 00 00 02
This field is defined in datastage a binary 9 signed, usage COMP.
i.e. PIC S9(9) COMP.
In my 7.5 job, this field is read with a value of 2.
In my 8 job , this field is read with a value of 8590127600
Any ideas?
Is this a bug, or has the move to version 8 exposed some incorrect settings in the filestage in my job?
Thanks.