sequential file warning

Post questions here relative to DataStage Enterprise/PX Edition for such areas as Parallel job design, Parallel datasets, BuildOps, Wrappers, etc.

Moderators: chulett, rschirm, roy

Post Reply
Karine
Participant
Posts: 37
Joined: Sun Feb 18, 2007 3:33 am

sequential file warning

Post by Karine »

I'm reading a sequential file with the following format
col1 char(3)
col2 char(5)
col3 char(8 )

and below are my sample data:
1112222233333333
4445555566666666

The sequential file stage has this definition:
Record Level - final delimiter = none
Field Level - Delimiter = none
Quote = none

This are the warnings I got in the Director log:

Sequential_File_0,0: Import consumed only 16bytes of the record's 17 bytes (no further warnings will be generated from this partition)
Sequential_File_0,0: Import warning at record 0:
Sequential_File_0,0: Missing record delimiter "\n", saw EOF instead
Sequential_File_0,0: Import warning at record 1:

Can someone help me by explaining why I'm getting the warnings? What did I do wrong? Why the first warning complained about the record has 17 bytes when to me it only has 16 (3+5+8= 16).


Thanks in advance.
Last edited by Karine on Mon Apr 02, 2007 3:21 pm, edited 1 time in total.
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Specify Record Length as "Fixed" and see if that helps. Also try specifying Record Delmiter as "DOS newline."
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
samsuf2002
Premium Member
Premium Member
Posts: 397
Joined: Wed Apr 12, 2006 2:28 pm
Location: Tennesse

Post by samsuf2002 »

DSguru2B wrote:Specify Record Length as "Fixed" and see if that helps. Also try specifying Record Delmiter as "DOS newline."
DSGuru2B- Can we use "DOS newline" when we are using UNIX?
hi sam here
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

It depends.
I had replied to a duplicate post here before I came across this one. Realizing that the other post was in the wrong forum, I had deleted my reply on that one and copied the reply over here, without paying attention to the OS.
If it is a unix file then use UNIX newline . If its a dos file copied over to unix in binary, then you can use DOS newline or follow Ray's instructions in that other post I referenced here in.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
Karine
Participant
Posts: 37
Joined: Sun Feb 18, 2007 3:33 am

Post by Karine »

Sorry for the confusion and the wrong post. My OS is windows.

I've following Ray's suggestion :
Record Level - Final delimiter = none
Record delimiter string = \r\n (dos format)
and still the warning said

Sequential_File_0,0: Missing Delimiter "\r\n", saw EOF instead
Sequential_File_0,0: Import warning at record 1

What can be the explanation? Please help me to understand.
novneet
Participant
Posts: 28
Joined: Tue Jan 17, 2006 2:19 pm
Location: PUNE(INDIA)

Post by novneet »

Delete the property "QUOTE" completely, and then try it out.
Regards,
Novneet Jain
Karine
Participant
Posts: 37
Joined: Sun Feb 18, 2007 3:33 am

Post by Karine »

I have remove "Quote" property but still got the same warning.
Any other suggestions? This is really bugging me.
DSguru2B
Charter Member
Charter Member
Posts: 6854
Joined: Wed Feb 09, 2005 3:44 pm
Location: Houston, TX

Post by DSguru2B »

Delete the Record Delimiter and keep the Record Delimiter String. See if that helps. Also, view the file with a hex editor and see what do you have at the end, exactly.
Creativity is allowing yourself to make mistakes. Art is knowing which ones to keep.
us1aslam1us
Charter Member
Charter Member
Posts: 822
Joined: Sat Sep 17, 2005 5:25 pm
Location: USA

Post by us1aslam1us »

Code: Select all

  Record Level - Final delimiter = \n (Dos Format)
  Record delimiter string = none
That should be enough unless you have any other thing as a record delimiter. As suggested by DsGuru read your file in hex editor and check what exactly is your record delimiter.
I haven't failed, I've found 10,000 ways that don't work.
Thomas Alva Edison(1847-1931)
Post Reply