importing a file with record delimited by HEX 0A

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
suneyes
Participant
Posts: 82
Joined: Mon Jul 21, 2008 8:42 am

importing a file with record delimited by HEX 0A

Post by suneyes »

Hi all,
I have a job copying the same file to another file using two sequential file stages.I have a problem while importing this file which is a fixed width file 0f 150 charecters length and and has a HEX 0A at the end of each record.
I am taking the record length as char(151).
with properties
final delimites=end
delimiter=none and Quote=none.
all the records are not getting imported giving a warning message that "Field "RECORD" with 'delim=end' did not consume entire input"
"Input buffer overrun at field "RECORD"
"Import warning at record 0"


I tried taking the record properties as VARCHAR(151) the import was successful.
will there be any problem if i change the char field to varchar field.
please provide some inputs to my problem.

ps:i need to use the same job design as it a alreay productionised job.
sun
bcarlson
Premium Member
Premium Member
Posts: 772
Joined: Fri Oct 01, 2004 3:06 pm
Location: Minnesota

Post by bcarlson »

I think you need to set the record delimited to 'UNIX newline'. If you choose to import with the record length of 151, then give the final 'field' a filler-type name and drop it using the 'drop on input' option.

Brad
It is not that I am addicted to coffee, it's just that I need it to survive.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

Observe that 0A (hex) is 10 (decimal). This is a regular UNIX newline (or linefeed if you prefer that terminology).
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
suneyes
Participant
Posts: 82
Joined: Mon Jul 21, 2008 8:42 am

Post by suneyes »

Thanks Mr.bcarlson.
this helped me in resolving my issue..
HEX 0A is unix new line charecter!
I wouldn't have known it..Thanks ray.
sun
bcarlson
Premium Member
Premium Member
Posts: 772
Joined: Fri Oct 01, 2004 3:06 pm
Location: Minnesota

Post by bcarlson »

If the problem is resolved, make sure the mark the topic resolved, too!

Thanks!

Brad.
It is not that I am addicted to coffee, it's just that I need it to survive.
Post Reply