0
Mcl 
2500 pts. | Jun 26 2009 7:19AM GMT
I’ve seen this problem… 10 years ago. And it had to do with and EDI transmission, too.
I think what we did was create the file on the 400 and then FTP into that file.
I can’t say for sure, but its worth a try.
Regards
Mike
Bobcour 95 pts. | Jun 26 2009 11:57AM GMT
i don’t think so, becuase if you create a file with a record length
the file ftp’d could be any record length.
comes in as one long string.
thanks anyway
RonKoontz 1345 pts. | Jun 26 2009 1:24PM GMT
We FTP to the IFS and use gentran to process it. It works great. I checked and it also comes in as one string. Another place I was at I generated a program to read the IFS file one character at a time to generate/break at the segmants I needed. If you want an example program I think I still have it. Just email me if you want it. <a href="mailto:rkoontz@ceioh.com" title="mailto:rkoontz@ceioh.com">rkoontz at ceioh.com</a>. Thanks
Bobcour 95 pts. | Jun 26 2009 1:32PM GMT
but on the 400 PF you would have a record length,if you create the file coming in
the record length would be in the thousands.
isn’t the problem the sender not having a end of record code.
if brought in on PC notepad and convert to msdos its okay
RonKoontz 1345 pts. | Jun 26 2009 2:57PM GMT
The IFS its NOT a PF. IF you do not have a 3rd party software that is going to read the “big string” then you have to read it as a text file.
Or convert it when the FTP part starts.
Bobcour 95 pts. | Jun 26 2009 3:15PM GMT
i do have 3rd party software, but it needs a 80 or 132 position record
harbinger TrustedLink EDI/400 Version 2
Bobcour 95 pts. | Jun 26 2009 3:49PM GMT
the thing is i get edi files from another client and its fine
comes in as multi records
it got to be something on there side. not having a end of record(line feed)
