|
This is a lengthy message about a bisynch line problem that I have IBM stumped on. My site communicates our AS400 to a remote site via a BSC line. We use an ICF file and an online COBOL program to send and receive small transaction files. The remote site I dial into is a PC running commercial 3780 communication software. We dial in daily to receive a small file (@30 records). This works fine. The problem is every week we try to receive a larger file(same structure just more records, usually 1200). This larger file fails everytime. My communication trace shows I get about 4 packets of data and then the two computers go into a loop where the remote sends me a '2D' request and mine acknowledges with a '1070'. This repeats about 10 times until the AS400 gives up and end the transmission. The remote site's trace shows the same series of characters being exchanged. Level 2 of IBM support says my configuration is fine and they have no suggestions. I talked to the higher level support for the commercial software vendor of the remote site and they are equally stumped. Nobody has any further answers or advice. They all say all configurations are fine. My question(s): Where do I go from here? Has anyone else experienced hangups with bisynch lines like this? I need to use a BSC line to be compatible with the remote site. Yes, I have reviewed the manuals but they don't offer a clue. Thanks +--- | 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.