Records skipped when reading sequential file

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
Pk39565
Premium Member
Premium Member
Posts: 34
Joined: Tue Dec 25, 2007 12:03 am
Location: Brisbane

Records skipped when reading sequential file

Post by Pk39565 »

Hi,

I have created a sequential file manually which has following data

Code: Select all

R00450000010100|ONE|ACTIVE|90286|DIRECT|2010-01-10|2011-01-10
R004P0000010100|ONE|ACTIVE|90286|DIRECT|2008-05-20|2011-01-10
R004000010100|ONE|ACTIVE|90286|DIRECT|2007-03-10|2011-01-10
When I read the above data in sequential file in parallel job only last row is showing the data, the first 2 records are skipped.

Property of sequential files:
Delimter=|
Final Delimeter =end (used none also ..result is same)

why the first 2 records are skipped? was there any format issues?

thanks in advance
adityavarma
Premium Member
Premium Member
Posts: 104
Joined: Thu Jul 12, 2007 11:32 pm
Location: Canada

Re: Problem with sequntial file

Post by adityavarma »

Are you getting any warnings while running the jobs?

See if there is any filter condition applied in the sequential file stage
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

What are the data types you've used for the columns in the stage?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Look in the job log. Are they being skipped, or are they experiencing import failures and being rejected/dropped?
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
mk_ds09
Participant
Posts: 72
Joined: Sun Jan 25, 2009 4:50 pm
Location: Pune

Post by mk_ds09 »

Hi

Check the first column values in all three records

R00450000010100|ONE|ACTIVE|90286|DIRECT|2010-01-10|2011-01-10
R004P0000010100|ONE|ACTIVE|90286|DIRECT|2008-05-20|2011-01-10
R004000010100|ONE|ACTIVE|90286|DIRECT|2007-03-10|2011-01-10

You need to check the first column metadata, it seems that metadata is not defined correctly.

All other columns are having the same values, so should not be any issue with those columns.

Also check the last character after each record, either through unix or some editing tool..

Hope this helps..
-----------------------------------
Regards
MK

What would you attempt to do if you knew you could not fail?

-----------------------------------
abc123
Premium Member
Premium Member
Posts: 605
Joined: Fri Aug 25, 2006 8:24 am

Post by abc123 »

Do a:
od -c YourFileName

This'll tell you what the last character is.

You need to have Quote=None in Field Delimiter as well. None is not the default.
Post Reply