|
David At 09:35 PM 11/8/97 +0500, you wrote: >On a related note, we are just switching to the dreaded NT desktops and >are using the Client Access 5250 emulator over Telnet. The sessions are >not timing out after they reach the Telnet inactivity timeout limit. Has >anyone else experienced this, and do they know why? The Rumba sessions >under Win 3.1 always used to timeout correctly. Are you referring to the session on the PC or on the 400? I find that CA does not check for a live connection. This engenders many problems and some odd behavior, from my experience. OTOH, if you execute NETSTAT on the 400 and take option 3, you'll see the connections there, including one (or more) with your PC's IP address. I believe that these connections will terminate according to the TELNET attributes. Unfortunately, CA does not try to determine, as I said, whether these things are live. Are you listening, IBM? Vernon Hamberg Systems Software Programmer Old Republic National Title Insurance Company 400 Second Avenue South Minneapolis, MN 55401-2499 (612) 371-1111 x480 +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to "MIDRANGE-L@midrange.com". | To unsubscribe from this list send email to MAJORDOMO@midrange.com | and specify 'unsubscribe MIDRANGE-L' in the body of your message. | 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.