Sequential file stage- low value

[suresh_dsx]

|i,
We are getting a binary file[delimited with "|"] as source. It is not giving as proper view data , While Reading the file using sequtial file stage, given options as EBCDIC with binary format in the stage. but we are not getting proper view data.

Code: Select all

Sampel Seq file stage view data -

10|abcd|100000
1|2|3|4|5|asdadad|349038403984|sdjkflksjdlajd
1|2|3|4|5|asdadad|349038403984|sdjkflksjdlajd
1|2|3|4|5|asdadad|349038403984|sdjkflksjdlajd
40|abcd|100000

We need to give the lowvalue "X00", but i did not see any option which i need to give the low value in the sequential file stage.
Based on the forums, we need to use CFF stage but we already used sequential file stage, did not find the inforamtion after Reading the documentation which is provided by the datastage, givin more information on the ASCII but not on the EBCDIC format.
Exptect view data
as


Sampel Seq file stage view data -

Code: Select all

10|abcd|100000 
1|2|3|4|5|asdadad|349038403984|sdjkflksjdlajd 
1|2|3|4|5|asdadad|349038403984|sdjkflksjdlajd 
1|2|3|4|5|asdadad|349038403984|sdjkflksjdlajd 
40|abcd|100000

Thanks
Smartpal

[FranklinE]

Some background would help:

Is the original EBCDIC source (from which the sequential file is created) also pipe delimited?

Is ths sequential file created strictly with EBCDIC?

Low-values are just a problem for us, because when we process in an ASCII environment it gets treated as a null character rather than just a space filler for fixed-length columns and records. Also, standard practice in Cobol is to use spaces (x40) to pad all character fields (PIC X), and low-values only for binary-numeric fields (PIC 9 COMP, COMP-3, etc.).

Final comment: the general standard for EBCDIC systems -- being most often mainframe -- is to not use any delimiters at all. Binary reads use the "implicit" setting for record format. Your upstream sources should comply with that, and it's when they don't that you have this sort of problem.