If you are interfacing with an IBM mainframe, you may find that inbound data
is formatted in 80 byte chunks. This is how our old MF-based Sterling data
was being generated, and OS-like operating systems and their keepers really
like 80-byte records. For the rest of the world that does not depend on
pre-determined lengths, go with the max.
Just my two cents.
Art Douglas
Graduate of the Old School - and movin' on
[EMAIL PROTECTED] wrote:
> Exactly how should an EDI file be formatted?
>
> Should the file have any carriage returns to break it into lines of 80
> characters?
> Should the file be one long string with no "line formatting"?
> Does the communications piece have a say so (bysinch, asynch, ftp, pop3,
> http, sneaker-net, etc.)?
> Do the VANs change a file's format in transit?
> Should translators accept either (maybe a setting that can be switched
> could be provided)?
>
> What say you List?
>
> Thanks for your help.
>
> Jaime E. Zepeda
> Electronic Commerce Specialist
> Power & Telephone Supply Company
>
> =======================================================================
> To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
> To subscribe, mailto:[EMAIL PROTECTED]
> To contact the list owner: mailto:[EMAIL PROTECTED]
> Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
=======================================================================
To signoff the EDI-L list, mailto:[EMAIL PROTECTED]
To subscribe, mailto:[EMAIL PROTECTED]
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
