Yes, since FTP is an ASCII protocol, the Hex 0D is not an acceptable
character and will cause problems if sent via FTP to Sterling.  What's
troublesome is that you CAN pick up data using FTP that contains the Hex
0D, you just can't send it!  This, of course, causes problems if your
translator echoes the delimiters sent to you when generating
acknowledgements.  We've run into this quite a bit, especially with our
Carriers, who appear to favor the Line Feed as a delimiter.  Hence, we must
perform a delimiter conversion on all of our mailboxes at the VAN before
picking up, to insure we do not receive any Hex 15 (Line Feed) characters.

Suzanne Nichols




                    Michael Mattias
                    <michael.mattia        To:     [EMAIL PROTECTED]
                    [EMAIL PROTECTED]>             cc:
                    Sent by:               Subject:     Re: Is anyone else having the 
same Sterling Issues? No, I
                    Electronic Data        don't m ean the over paying issue.
                    Interchange
                    Issues
                    <EDI-L@LISTSERV
                    .UCOP.EDU>


                    09/15/00 04:02
                    PM
                    Please respond
                    to Michael
                    Mattias





I had that exact same problem right down to the funky 'ae' character with
Ordernet - excuse me, "Commerce:Network" - when I tried to send data which
used CR (x'0D') as the segment terminator.

However, I'm not sure that was the whole problem, as I was sending it using
the Dynacom Software package bundled into Mercator (TSI) Trading Partner
PC/32. Both Mercator and Sterling assured me the data was sent (Mercator)
and received (Sterling) as a pure datastream with no special interpretation
of control characters.

At least one of them was clearly misinformed, as I solved the problem by
changing the segment terminator to tilde (~). After I did that, all was
cool.

(FWIW, VICS should be shot for recommending x'0D' as the segment
terminator.
Heck, even the US Federal Government knows better: The HCFA Medicare EDI
guide states that while x'0D' is technically valid as a delimiter or
terminator, use should be avoided as CR is a control character on some
systems. They say the same thing about line feed and both horizontal and
vertical tabs).

Michael C. Mattias
Tal Systems
Racine WI
[EMAIL PROTECTED]


----- Original Message -----
From: Anthony Beecher <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, September 15, 2000 1:00 PM
Subject: Re: Is anyone else having the same Sterling Issues? No, I don't m
ean the over paying issue.


> I have had a problem where Sterling has mangled my data by inserting some
> weird  character. It has happened twice with no changes on my end (and
gone
> away twice with no changes on my end).  What happenes it the data will
show
> up on their report website with some funny gaelic AE character sprinkled
> through it.
>

=======================================================================
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/

Reply via email to