The TN3270 reconnect failure is one of THE most annoying things about remote mainframe work.
Reconnect worked so well in the "good old SNA days," I keep thinking that the TSO/Comm Server/whatever folks have not really accepted that TN3270 is here to stay, and ought to be made to work well, not merely to work. Charles -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Edward Jaffe Sent: Monday, January 15, 2007 9:57 AM To: [email protected] Subject: TSO RECONNECT (Was: Interrupting DSLIST) Steve Comstock wrote: > Walt Farrell wrote: >> Also, to get RECONNECT working again, have your network system >> programmers look at the TN3270 parms. There's one in there (sorry, I >> don't know which one) that affects detection of disconnected >> terminals that should allow faster detection of your disconnection, >> and thus allow RECONNECT to work. >> >> Walt > > Tested it out, worked like a champ! Thanks for that > little technique, Walt. What technique? What was the name of the TN3270 parameter you changed? What had you coded before? What have you coded now? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
