EBCIDIC to ASCII using CFF having COMP3 filed

venkateshkumarg · Post by **venkateshkumarg** » Tue Mar 24, 2015 11:40 am

We are trying to convert EPCIDIC file using Complex Flat File stage. one of the record is having COMP3 filed to convert. when we have all the field defined as character, job runs successfully and write the data into a sequential file. only issue is COMP3 field shows junk value.
If we make COMP3 field as decimal (11,2), Job throws an error as below.

Complex_Flat_File_0,0: Tag value from link is unavailable; for field "complex_flat_file_0_record_type"

Complex_Flat_File_0,0: Import unsuccessful at record 2.

FYI. when I view from the CFF stage, I could able to view COMP3 field data properly for only one record

chulett · Post by **chulett** » Tue Mar 24, 2015 1:23 pm

Perhaps this FAQ entry will help.

FranklinE · Post by **FranklinE** » Tue Mar 24, 2015 2:29 pm

Craig,

I now have significant experience with CFF stage, and have a short list of additions to the FAQ available. Let me know how you wish to use it.

Venkatesh,

The FAQ will definitely help you, but it doesn't say much about how to use the Table Definition Import wizard for COBOL FD metadata. A couple of cautions:

Be sure to get a text-file version of the copybook in use. This is critical for accurately (and efficiently) creating your table definition.

1) Remove all "88" level lines. They translate into description text only, and have no use otherwise.

2) Remove all comment lines -- "*" in column 7 of the copybook. Same deal as "88" level lines.

3) Consider splitting out "REDEFINES" into separate text files for import. You will need advice from your COBOL developers on how it's being used.

chulett · Post by **chulett** » Tue Mar 24, 2015 3:12 pm

FranklinE wrote:Craig, I now have significant experience with CFF stage, and have a short list of additions to the FAQ available. Let me know how you wish to use it.

Send me the additions in a PM and I'll add them to the FAQ, that or send me a fully revised FAQ if you prefer and I'll replace the contents.

venkateshkumarg · Post by **venkateshkumarg** » Tue Mar 24, 2015 3:15 pm

Hi Frank,

Looks like my copybook/text file imported good. I could able to read/view first line, It gives me an error for 2nd line onward
Like [####] Data Browser - ERROR.

What could have been an issue here.

ray.wurlod · Post by **ray.wurlod** » Tue Mar 24, 2015 4:26 pm

Obviously an ERROR occurred.

(The message tells you no more than that.)

Have a look at the imported table definition then compare that with what's actually in the file. Don't use DataStage for this latter activity.

FranklinE · Post by **FranklinE** » Wed Mar 25, 2015 9:52 am

Send me the additions in a PM and I'll add them to the FAQ, that or send me a fully revised FAQ if you prefer and I'll replace the contents.

I'm in a bit of a bind right now. I'll decide which form to use and send it as indicated. Thanks.

priyadarshikunal · Post by **priyadarshikunal** » Fri Mar 27, 2015 2:06 am

If you are getting error in COMP fields only, I believe the file was FTPed in Ascii mode which may lead to data corruption in COMP fields. Make sure the file was transferred in binary mode.

And yes, you need to have a good look on the cobol file definition as well.