Issue with reading a EBCDIC Cobol file - Complex file stage
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 247
- Joined: Thu Apr 27, 2006 6:38 am
- Location: Hyderabad
Issue with reading a EBCDIC Cobol file - Complex file stage
Hi All,
I am trying to read a EBCIDIC file using a CFF stage. I get the following error:
Complex_Flat_File_0,0: Short read encountered on import; this most likely indicates one of the following possibilities:
1) the import schema you specified is incorrect
2) invalid data (the schema is correct, but there is an error in the data). [new-impexp/file_import.C:3227]
Also some more details before this fatal error
Complex_Flat_File_0,0: Field "WMM_CROSS_RFRN_ACCT_NR" has import error and no default value; data: {0c 00 0c 00 0c L 00 00 0c @ @ @ @ @ @ @}, at offset: 33 [impexp/group_comp.C:7679]
Following are the options set
Record type: Fixed
Byte-order: Native-Endian
character set: EBCDIC
Data format: Binary
Record delimiter:
Separator: Project default
I renamed the copied the copybook as .cfd and imported the same as As Is.
Could any one help to find out the reason please
Thanks
Devi
I am trying to read a EBCIDIC file using a CFF stage. I get the following error:
Complex_Flat_File_0,0: Short read encountered on import; this most likely indicates one of the following possibilities:
1) the import schema you specified is incorrect
2) invalid data (the schema is correct, but there is an error in the data). [new-impexp/file_import.C:3227]
Also some more details before this fatal error
Complex_Flat_File_0,0: Field "WMM_CROSS_RFRN_ACCT_NR" has import error and no default value; data: {0c 00 0c 00 0c L 00 00 0c @ @ @ @ @ @ @}, at offset: 33 [impexp/group_comp.C:7679]
Following are the options set
Record type: Fixed
Byte-order: Native-Endian
character set: EBCDIC
Data format: Binary
Record delimiter:
Separator: Project default
I renamed the copied the copybook as .cfd and imported the same as As Is.
Could any one help to find out the reason please
Thanks
Devi
-
- Participant
- Posts: 247
- Joined: Thu Apr 27, 2006 6:38 am
- Location: Hyderabad
Unfortunately this often ends up being an iterative process. With big copybooks I will delete all but the first 20 columns or so, replacing it with a big VarChar filler field then check with "view data" to see if the columns are parsed correctly. When that is fixed, I will make a copy of the original and use the first 40 columns to check the next 20 for validity, and so on.
Often the errors come from COMP-3 columns not being interpreted correctly, or OCCURS being flattened incorrectly. Do you have either of these in your copybook?
Often the errors come from COMP-3 columns not being interpreted correctly, or OCCURS being flattened incorrectly. Do you have either of these in your copybook?
-
- Participant
- Posts: 247
- Joined: Thu Apr 27, 2006 6:38 am
- Location: Hyderabad
-
- Participant
- Posts: 247
- Joined: Thu Apr 27, 2006 6:38 am
- Location: Hyderabad
-
- Participant
- Posts: 247
- Joined: Thu Apr 27, 2006 6:38 am
- Location: Hyderabad
-
- Participant
- Posts: 247
- Joined: Thu Apr 27, 2006 6:38 am
- Location: Hyderabad
-
- Participant
- Posts: 247
- Joined: Thu Apr 27, 2006 6:38 am
- Location: Hyderabad
-
- Participant
- Posts: 247
- Joined: Thu Apr 27, 2006 6:38 am
- Location: Hyderabad
-
- Participant
- Posts: 247
- Joined: Thu Apr 27, 2006 6:38 am
- Location: Hyderabad
When I flatten the arrays. The nubmer of warning I got was few. But the job aborted due to the same reason.
Complex_Flat_File_0,0: Short read encountered on import; this most likely indicates one of the following possibilities:
1) the import schema you specified is incorrect
2) invalid data (the schema is correct, but there is an error in the data). [new-impexp/file_import.C:3227]
Also I receive the same warnings as below before I get this fatal error:
Complex_Flat_File_0,0: Field "WMM_CROSS_RFRN_ACCT_NR" has import error and no default value; data: {@ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @}, at offset: 33 [impexp/group_comp.C:7679]
Complex_Flat_File_0,0: Short read encountered on import; this most likely indicates one of the following possibilities:
1) the import schema you specified is incorrect
2) invalid data (the schema is correct, but there is an error in the data). [new-impexp/file_import.C:3227]
Also I receive the same warnings as below before I get this fatal error:
Complex_Flat_File_0,0: Field "WMM_CROSS_RFRN_ACCT_NR" has import error and no default value; data: {@ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @}, at offset: 33 [impexp/group_comp.C:7679]
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact: