CFF Index file Problem...
Moderators: chulett, rschirm, roy
CFF Index file Problem...
Hi,
I have index cobol file...I tried to convert that by using CFF stage in server i gave both the option like the binary and the other but still it shows junk data...The file is indexed file...Also when i tired the same in Parallel it shows the same....I tired with various option it shows the same junk data...i could not figure out where it is going wrong..We have one tool to conver the copy books mainframe file to a flat file in that when we use the same file there is no problem so i felt there is no problem with copy books or the source fikle..so i think i am doin some thing wrong..If any body have dealt with index type of cobol files and can help me out will be great
Thanks,
I have index cobol file...I tried to convert that by using CFF stage in server i gave both the option like the binary and the other but still it shows junk data...The file is indexed file...Also when i tired the same in Parallel it shows the same....I tired with various option it shows the same junk data...i could not figure out where it is going wrong..We have one tool to conver the copy books mainframe file to a flat file in that when we use the same file there is no problem so i felt there is no problem with copy books or the source fikle..so i think i am doin some thing wrong..If any body have dealt with index type of cobol files and can help me out will be great
Thanks,
RK
Never done this, hence the 'possibly' part. And it would require purchasing ODBC drivers for this, nothing ships with DataStage that would handle the files in question. Or something like an iWay Adapter for VSAM or whatever you needed to access.
Since either would need to be purchased, I'll stick with the 'Best to arrange to get the data dumped to a flat file' advice I gave earlier.
Since either would need to be purchased, I'll stick with the 'Best to arrange to get the data dumped to a flat file' advice I gave earlier.
-craig
"You can never have too many knives" -- Logan Nine Fingers
"You can never have too many knives" -- Logan Nine Fingers
Actually the file that we have are ISAM files...Also As i am using latest version of Information Servers does that version support ISAM files?chulett wrote:Never done this, hence the 'possibly' part. And it would require purchasing ODBC drivers for this, nothing ships with DataStage that would handle the files in question. Or something like an iWay Adapter for VSAM or whatever you needed to access.
Since either would need to be purchased, I'll stick with the 'Best to arrange to get the data dumped to a flat file' advice I gave earlier.
RK
-
- Participant
- Posts: 47
- Joined: Fri Sep 23, 2005 6:01 pm
I used the CFF stage...but As you said i tried using the SEQ file stage setting the option you said i get the following errorDSguru2B wrote:What options did you try in px sequential file stage? Did you try, Format tab, under 'Defaults', String ----> Export EBCIDIC as ASCII ?
##E IIS-DSEE-TOIX-00158 11:59:31(000) <Sequential_File_50,0> Error reading on import.
##E IIS-DSEE-TFRS-00061 11:59:31(001) <Sequential_File_50,0> Consumed more than 100000 bytes looking for record delimiter; aborting
##E IIS-DSEE-TOIX-00179 11:59:31(002) <Sequential_File_50,0> Import error at record 0.
##E IIS-DSEE-TFOR-00089 11:59:31(003) <Sequential_File_50,0> The runLocally() of the operator failed.
##E IIS-DSEE-TFOR-00089 11:59:31(005) <APT_CombinedOperatorController,0> The runLocally() of the operator failed.
##E IIS-DSEE-TFPM-00040 11:59:31(006) <APT_CombinedOperatorController,0> Operator terminated abnormally: runLocally did not return APT_StatusOk
##E IIS-DSEE-TFSC-00011 11:59:37(000) <main_program> Step execution finished with status = FAILED.
thanks,
RK
My bad. Not the String, but under General, provide the Character Set as EBCDIC and Data Format as binary.
Along with that, set the Record Length as fixed and Final Delimiter as end.
Set up the each column properly in the column tab (I mean the metadata).
Along with that, set the Record Length as fixed and Final Delimiter as end.
Set up the each column properly in the column tab (I mean the metadata).
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
I did the way you said i get following errorDSguru2B wrote:My bad. Not the String, but under General, provide the Character Set as EBCDIC and Data Format as binary.
Along with that, set the Record Length as fixed and Final Delimiter as end.
Set up the each column properly in the column tab (I mean the metadata).
##E IIS-DSEE-TOIX-00179 12:32:12(002) <Sequential_File_50,0> Import error at record 1.
##E IIS-DSEE-TFOR-00089 12:32:12(003) <Sequential_File_50,0> The runLocally() of the operator failed.
##E IIS-DSEE-TFOR-00089 12:32:12(005) <APT_CombinedOperatorController,0> The runLocally() of the operator failed.
##E IIS-DSEE-TFPM-00040 12:32:12(006) <APT_CombinedOperatorController,0> Operator terminated abnormally: runLocally did not return APT_StatusOk
##E IIS-DSEE-TFSC-00011 12:32:18(000) <main_program> Step execution finished with status = FAILED.
Thanks for your help....
RK
You know what. Craig is right. VSAM cannot be accessed by sequential file stage. The files that I have at my current site are flat files with binary data (which triggered my suggestion) and not VSAM files. So, forget my suggestion altogether. Wait for someone to come by and shed some light on this. I think CFF stage is the way to go.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
you are right...I fixed the error but it shows same junk data as it showed in the CFF stage...I am going try calling IBM to check and see whether they support VSAM or ISAM files...If any body can can help me out with will be great.....DSguru2B wrote:You know what. Craig is right. VSAM cannot be accessed by sequential file stage. The files that I have at my current site are flat files with binary data and not VSAM files. So, forget my suggestion altogether. Wait for someone to come by and shed some light on this. I think CFF stage is the way to go.
RK
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
From Parallel Job Developer's Guide (version 7.5), Chapter 10 (Complex Flat File Stage):
In version 8.0, the Complex Flat File stage supports Multi Format Flat (MFF) file. Constraints can be specified on the output links to filter data and/or define when a record should be sent down the link.When used as a source, the stage allows you to read data from one of more complex flat files, including MVS datasets with QSAM and VSAM files.
When used as a target, the stage allows you to write data to one or more
complex flat files. It does not write to MVS datasets.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.