|
James, This is strictly a software issue on our side. My trading partner is willing to use ASYNCH. On Saturday, May 13, 2000 2:15 AM, James W. Kilgore [SMTP:eMail@James-W-Kilgore.com] wrote: | Eric, | | The purpose of most EDI packages is not just to get data from point A to | point B, but to verify that the data was delivered and done so | accurately. | | At it's simplest, bisync is handled by a pair of programs (one at each | end) that does a batch transmission of a file. This can be replaced | with FTP and appropriate byte count and check digit controls to provide | a degree of confidence in delivery. | | What this vendor may have is the EDI mapping within the bisync | communications program and performs their translation and verification | on a record by record or order by order basis. | | Now that's a different story. | | (thinking out loud) Instead of having the EDI communications running, | one could create an umbrella loop that uses FTP to send an order, | verify, process, feedback. Sort of like producing a report by opening | and closing the spool file on each page (one page = one order) while the | spool writer chugs away at what it's received. There is a performance | penalty. | | IMHO, by now, with the current technology, they should have figured this | out, on their own dime. Is there a trading partner issue that must be | addressed? Like available communications protocols? | | Ooops, I just heard the end of week, no thinking out loud buzzer go off. | ;) | | | Eric Kempter wrote: | > | > Is there a great deal of difference in the programming of Bisynchronous | > communications vs Asynchronous communications. We purchased an EDI package | > that uses Bisynch comms. We asked the vendor for a quote on how much it | > would cost to modify his package to support asynch comms. He said it would | > take him weeks to come up with a quote and then it would probably take | > months to program. Does this sound realistic. TIA | +--- | | This is the Midrange System Mailing List! | | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | | Questions should be directed to the list owner/operator: david@midrange.com | +--- +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.