George > ... and here's what the manual says:
First of all, when you refer to "the manual", please be aware that there could be many manuals covering a particular topic, so mentioning the name of the manual and the section within it where the text upon which you are relying appears is always helpful, even to the provision of an URL. In this case I was obliged to Google one of the sentences. Fortunately, I had only two his, one IBM representation of the manual and your post. > TIMEMARK is a telnet enhancement and here's what the manual says: The manual is z/OS V1R9 Communications Server, New Function Summary, GC31-8771-03, September 2007, and the section you quoted was the following: http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1F230/2.3.8 <quote> 2.3.8 Telnet enhancements In z/OS V1R8 Communications Server, Telnet is enhanced in the following ways: By specifying a new profile statement, you can direct Telnet to end SNA Telnet sessions that are unresponsive. This reduces the number of reconnect failures caused when Telnet still has a SNA session for the original connection. When a new connection request is received, the check client connection function sends a TIMEMARK value to every pre-existing connection associated with the client identifier of the new connection that is being established. If a response is not received, the connection is ended. </quote> There is an indeed an "enhancement" but it is *not* the invention of TIMEMARK. The "enhancement" is a new function which employs the long pre- existing TELNET TIMEMARK protocol which dates from the first "TN3270 Enhancements" RFC, 1647, July 1994. It is an enhancement, new in V1R8, to the Communications Server IP "TN3270E" server program. In principle, it introduces the idea that, rather than wait for typically a long period, up to 2 hours before checking that a TELNET TCP connection is still viable, a number of outstanding connections, within a group defined by a newly established TCP connection, can be checked. The pre-existing TELNET TIMEMARK protocol is used in order to perform the checking. This was designed mainly for the situation where a single workstation was supporting multiple TN3270 client emulator instances, all using the same client IP address and where the operative client identifier would be the client IP address. The enhancement uses the CHECKCLIENTCONN statement and, by default, the enhancement is switched off. Since I can see from your parameters that you have not specified CHECKCLIENTCONN - it is the asterisk under "C" in the PERSIS(TENCE) group - you are not using the TIMEMARK protocol in these circumstances. You are, however, using the TIMEMARK protocol in the context it has always been used, namely as a means to check after a period of inactivity on the concatenated SNA session/TCP connection There is yet another TELNET server function which uses TIMEMARK which has been introduced over the last decade or so. This is the "take over" function, implemented using the statements containing the characters "TKO" - not "NOTKO", the default, obviously! Chris Mason On Thu, 27 Jan 2011 11:43:02 -0500, George Rodriguez <george.rodrig...@palmbeachschools.org> wrote: >TIMEMARK is a telnet enhancement and here's what the manual says: > > - By specifying a new profile statement, you can direct Telnet to end SNA > Telnet sessions that are unresponsive. This reduces the number of reconnect > failures caused when Telnet still has a SNA session for the original > connection. When a new connection request is received, the check client > connection function sends a *TIMEMARK* value to every pre-existing > connection associated with the client identifier of the new connection that > is being established. If a response is not received, the connection is > ended. > >... >* >*George Rodriguez* ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
