I have sequential file landed using datstage. And I am using this file in another job. For testing purpose I had to edit this file once created for one record.
I am just changing one letter. I am doing this using vi.
Once I save this file and try to read this in datstage job i get import error.
However when i do not do any editing file is read okay in next job..
Any clues...
File gets currupt if edited in vi.
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Umm... don't use vi ?
Examine the file with a hex-capable editor to determine what the line terminator character(s) (if any) are.
What precisely do you mean by "corrupted"? That is, what error do you get? What raw record is sent to the reject link?
Examine the file with a hex-capable editor to determine what the line terminator character(s) (if any) are.
What precisely do you mean by "corrupted"? That is, what error do you get? What raw record is sent to the reject link?
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.
-
- Participant
- Posts: 94
- Joined: Wed May 08, 2002 8:44 am
- Location: Germany
- Contact:
Re: File gets currupt if edited in vi.
Check if you have written the file with varchars. You might have the option "varchar prefix byte" active. This bytes may get corrupted when using vi.
In this case you better write the file without varchar prefix bytes. Have a look at the schema definition.
Best regards
Klaus
In this case you better write the file without varchar prefix bytes. Have a look at the schema definition.
Best regards
Klaus