Issue with reading a EBCDIC Cobol file - Complex file stage

devidotcom · Post by **devidotcom** » Mon Feb 25, 2008 4:24 am

The parameter already has a space assigned to it.

ArndW · Post by **ArndW** » Mon Feb 25, 2008 4:37 am

WMM_CROSS_RFRN_ACCT_NR is probably a COMP-3 field and the error means that your metadata doesn't match the data. There is no easy way to solve this, you need to match the metadata with the data column by column to find out where the difference occurs. Assume the OCCURS didn't work correctly as a starter.

devidotcom · Post by **devidotcom** » Mon Feb 25, 2008 4:41 am

No that column is not Comp-3 column

ArndW · Post by **ArndW** » Mon Feb 25, 2008 4:43 am

Ok, that means the error has occurred before that column. You will still need to put in some time and effort in locating the cause.

Aruna Gutti · Post by **Aruna Gutti** » Mon Feb 25, 2008 2:35 pm

Where is your data coming from ? Did you checked whether your data is actually in binary format ?

Usually I get this kind of error when I ftp the data in ASCII format instead of binary by mistake.

Regards,

Aruna.

Aruna Gutti · Post by **Aruna Gutti** » Mon Feb 25, 2008 2:39 pm

Where is your data coming from ? Did you checked whether your data is actually in binary format ?

Usually I get this kind of error when I ftp the data in ASCII format instead of binary by mistake.

Regards,

Aruna.

devidotcom · Post by **devidotcom** » Tue Feb 26, 2008 1:00 am

Yes its in binary format only. I was told its a EBCDIC file.

devidotcom · Post by **devidotcom** » Tue Feb 26, 2008 4:49 am

I put default values for each column manually and was able to read the records.
But the job yet aborts with the 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]

So should I assume that the data is wrong but the schema is right?

Aruna Gutti · Post by **Aruna Gutti** » Tue Feb 26, 2008 4:56 am

Looks like data problem to me. Did you tried viewing your data in some kind of editor like UltraEdit to determine the validity. I struggled initially with this problem when I tried my CFF to work. Once I did the binary ftp properly it worked.

devidotcom · Post by **devidotcom** » Tue Feb 26, 2008 5:44 am

Yes I guess its the issue with the data. As AndW mentioned. I will check and update on the same

devidotcom · Post by **devidotcom** » Wed Feb 27, 2008 2:42 am

Hi I am trying to analyze the binary data using Ultraedit...
I am new to using Ultraedit tool. I find mhy records to be like following. I am not sure if it has junk data. Can anyone explain.

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@

ray.wurlod · Post by **ray.wurlod** » Wed Feb 27, 2008 3:27 am

You might have a whole lot of "@" characters, you may have a whole lot of NUL characters (0x00). Switch to hex mode to determine which it is.

ray.wurlod · Post by **ray.wurlod** » Wed Feb 27, 2008 5:33 am

It may mean that your conversion from EBCDIC to ASCII was not done correctly. You don't convert binary (COMP) columns, for example.

devidotcom · Post by **devidotcom** » Wed Feb 27, 2008 5:51 am

I just use the option from File->Conversion->EBCDIC to ASCII in the Ultra edit and to the convert.

How do I convert COMP columns? Please advice

ArndW · Post by **ArndW** » Wed Feb 27, 2008 10:51 am

You cannot convert COMP-3 columns in that manner within the editor. Do you have ANY columns in your COBOL that are "COMP" or "COMP-3" or "COMP-2"?