|
>I am experiencing the same problem with a customer. I have been talking >with IBM in Rochester about this situation. The customer is not using ANY >Win 95, only Win 98. We are narrowing it down hopefully it maybe a TelNet >or 5250 problem. > >Currently, we are waiting to get a comm trace while we have a telnet & CA >5250 session going. The theory is if CA dies and telnet session is still >alive then a 5250. If both die then telnet issue. Either case, the >findings will have to go back to the develpoers for analysis. > >After CA session dies we are still able to Ping to AS400. Here's another thought: download a TN5250 client such as that available from www.mochasoft.dk (a licensed version is only $25 single user or $250 per company) and connect with it. Use it long enough to determine if the problems are AS/400-Telnet-IP stack-related or if they are inside CA/400. Has the oily smell of CA/400 roadkill to me! rp +--- | 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.