Charles Read RFC 2355. You'll see that the full implementation of Unformatted System Services (USS) LOGOFF is not permitted when the LOGOFF command has to be processed by the TN3270E server. In fact, since two modes of behaviour for USS commands, "passthrough" or "non-passthrough", are defined in RFC 2355 and a TN3270E client has no idea which flavour of TN3270E server it is talking to, there's no reason - except for a lack of imagination on the part of the Communications Server (CS) IP developers - why CS IP could not implement USS LOGOFF with all its operands including the TYPE operand.
I discussed - perhaps argued would be a better verb - this topic in a thread "TN3270 Question" started just over a year ago - to which I see you contributed.[1] See particularly my reply to Pat O'Keefe of Fri 20 Jan 2006 03:45 and my reply to Shmuel Metz (who was still talking to me a year ago) of Fri 20 Jan 2006 20:43. Chris Mason [1] Search on "2355" in Google Groups and click "Sort by date". ----- Original Message ----- From: "Charles Mills" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <IBM-MAIN@BAMA.UA.EDU> Sent: Monday, 15 January, 2007 8:22 PM Subject: Re: TSO RECONNECT (Was: Interrupting DSLIST) > 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 ---------------------------------------------------------------------- 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
