I am using DataStage XE Ver. 7.51 on HP Unix box. One of our mainframe job zips and then FTP's a file from mainframe to Unix using binary mode. This file has one field as Packed PIC S9(7) COMP-3. When I use this file in the CFF Stage (After unzipping on Unix), it does not show the correct value. On the mainframe it has a value of 123199 ('0123199F' with HEX ON) but on the Unix it shows '29038863'. I am using this field as BINARY (7) in the CFF stage. Can someone please let me know why CFF is not converting it properly and how to fix this issue.
Thanks.
Packed Field not converted properly with CFF Stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 31
- Joined: Wed Feb 04, 2004 2:04 pm
- Location: Canada
-
- Participant
- Posts: 31
- Joined: Wed Feb 04, 2004 2:04 pm
- Location: Canada
-
- Participant
- Posts: 31
- Joined: Wed Feb 04, 2004 2:04 pm
- Location: Canada
I'm not all that familiar with the CFF stage, but from what I recall declaring something a BINARY would be equivalent to a COBOL COMP-1 field, not a COMP-3. Seems like there would be a different choice you should make for COMP-3 - something like Packed or Packed Decimal perhaps?
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
-
- Participant
- Posts: 31
- Joined: Wed Feb 04, 2004 2:04 pm
- Location: Canada
And yet oddly enough you can specify COMP-3.
As noted in the online help, you can right-click on the Source Column row for that field and select 'Edit Row'. In the COBOL definition in the bottom half you'll find a Usage option, where COMP-3 is one of the valid values.
As noted in the online help, you can right-click on the Source Column row for that field and select 'Edit Row'. In the COBOL definition in the bottom half you'll find a Usage option, where COMP-3 is one of the valid values.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers