|
[EDI-L Mailing List Archive Home]
[Message List]
[Reply To This Message]
RE: Urgent GXS bisync unrecognized comm session failure issue
Hi Dawn:
We are using TL EDI400 and dialing GXS. I confirmed with them on Friday
(2/28) that the local dial number we are using in Atlanta would continue to
work after Saturday. I just checked our system and it indeed is still
working. GXS would not commit to me how much longer it would work and
strongly suggested that I open a case immediately with the migration team to
move to IP. (However since the migration team is in London, they were not
available when I called, good luck West Coasters).
I did not have the heart to tell him that I would only need the BSC support
for another week or 2 as we are parallel testing our direct FTP connection
to our only partner that we used GXS for. We probably would never have
changed the connection, but GXS's strong arm made us doing something, and
that something was cutting them out of the process.
cjg
Carl J. Galgano
EDI Consulting Services, Inc.
550 Kennesaw Avenue, Suite 800
Marietta, GA 30060
(770) 422-2995 - voice
(419) 730-8212 - fax
mailto:
http://www.ediconsulting.com
AS400 EDI, Networking, E-Commerce and Communications Consulting and
Implementation
http://www.icecreamovernight.com
Premium Ice Cream Brands shipped Overnight
"You ain't gonna learn what you don't want to know" - rw
-----Original Message-----
From: Field, Dawn [mailto:
Sent: Tuesday, March 04, 2003 2:53 PM
To:
Subject: [EDI-L] Urgent GXS bisync unrecognized comm session failure issue
Just an FYI for those out there that are using Inovis TL EDI400 (maybe other
software affected too) with the new 866 phone # provided by GXS (formerly
GEIS) recently to continue bisync connections we have discovered a big
problem. Something has changed on the new # connecting to the network for
failure responses. Our Software is not recognizing the failure. There are
2 things that we have witnessed 1 the session hangs for hours until visually
recognized and a hard cancel on the job is initiated by a user or 2 the comm
session completes normally but the edi docs were never sent to the VAN. The
first one is easy to respond to and recognize, but the second one is
completely hidden to us. In our software there is no recognized indication
of failure. The comm session has a completed normal status. The way I
found it was a vendor indicated a missing block of control #'s and I went
out and pulled a billable sender status report and sure enough the block of
control #'s were missing. In my software it all looked like it sent fine.
So if you recently switched to the new # that is supposed to be available
for bisync till June I believe be aware there are issues and you may want to
require going back to your old phone #. Check it out quick because the VAN
only holds docs for 3 days including weekend so we have already lost the
tracking for Friday's business. We switched back on 2/21/03 so I have to
come up with another way to identify the missing control #'s from 2/21 to
2/28. Good luck! Dawn
Dawn Field
Sr. IT Developer
Medtronic Information Technology
------------------------ Yahoo! Groups Sponsor ---------------------~--> Get
128 Bit SSL Encryption!
http://us.click.yahoo.com/LIgTpC/vN2EAA/xGHJAA/OIFolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, send an email to:
Message Identifiers: <SALES>, <JOBS>,
<LIST>, <TECH>, <MISC>, <EVENT>, <OFF-TOPIC> Access the list online at:
http://groups.yahoo.com/group/EDI-L
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
|
 |
Subscribe in XML format
| RSS 2.0 |
|
| Atom 0.3 |
|
|
Cart
