Lines in TIMPORT source file too long

Post Reply
barry.marcus
Posts: 288
Joined: Thu Nov 16, 2006 1:05 pm

Lines in TIMPORT source file too long

Post by barry.marcus »

I have a situation where some lines in my code-generated timport source files are apparently too long for the TIMPORT utility. When TIMPORT encounters these lines during the loading of the data, an ABEND is generated. The issue is not with too much data per record, nor (I don't think) too much data in any one field. The problem is just excessively long lines in the source text files themselves. I can easily change my source file generation code to break these lines into multiple shorter lines, but I don't know what the maximum length of a line should be. The longest line I've encountered so far >100K characters, which apparently is too long.

Thanks for your help.
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

Lines in TIMPORT source file too long

Post by mark »

All I can think of is older versions with csv data that might cause that. What's your data format? csv or something else?
What's your timport version and release reported by timport -h ?
barry.marcus
Posts: 288
Joined: Thu Nov 16, 2006 1:05 pm

Lines in TIMPORT source file too long

Post by barry.marcus »

Version 2.12 Release: 20040720 (Non-Client/server)

And yes... We've set up our data files as comma separated values with our own custom delimiters defined in schema files
User avatar
mark
Site Admin
Posts: 5519
Joined: Tue Apr 25, 2000 6:56 pm

Lines in TIMPORT source file too long

Post by mark »

I don't see any reason it shouldn't work in that version. But the allocation unit is 30000 bytes so you might try line lengths shorter than that. But I doubt that will change anything since it's the length of the entire record that I would expect to matter.

If it still doesn't work you may need to open a ticket with your schema and some sample data.
barry.marcus
Posts: 288
Joined: Thu Nov 16, 2006 1:05 pm

Lines in TIMPORT source file too long

Post by barry.marcus »

You're right. That didn't work. But I found the issue. Dumb mistake. I just had to increase the allowed size of the record in the schema file.

Thanks for the help
Post Reply