I saw something like that one time when working with Ordernet - excuse me,
of course I meant "Commerce:Network." (This is maybe a year ago.)
Turns out it was caused by using 'carriage return' (ASCII x'0D') as the
segment terminator (as suggested by VICS). Commerce:Network's system thought
"CR" meant "CRLF" and therefore "newline" and started a new physical record,
space-filling the rest of the current record when it found CR at other than
a communications record boundary.
Check your delimiter and terminator characters; if they are any kind of
"control" characters (especially CR or LF (ASCII x'0A') ) replace them with
non-control characters and try again. (It's worth a shot).
Michael C. Mattias
Tal Systems
Racine WI
[EMAIL PROTECTED]
>
> Okay, I can't figure this out, so I thought that I would ask the group.
> First of all, my EDI system is TLE version 4.1.4 on a Unix platform. I
set
> up a separate Communications Mailbox within Ops Center and because of
that,
> I also created a separate bisync/API script (we have Cleo 3780Plus)
> specifically for that separate mailbox. Actually, the script was copied
> from another script that we're currently using for our main production
> mailbox at the VAN.
>
> Anyway, when the modem dials in and grabs EDI data from this new mailbox,
I
> get EDI data that looks like below:
>
> RISA*00* *00* *01*1319R2979LH *01*196238684H
> *010522*152GS*LB
> *131905978*196238684H*010522*1529*2*X*003030
> ST*823*000000002
>
> N1*BK*BIGTIMER BANK*1*13
> 1201228
=======================================================================
To contact the list owner: mailto:[EMAIL PROTECTED]
Archives at http://www.mail-archive.com/edi-l%40listserv.ucop.edu/
