Richard, The telnet server tried to send something out of connection 100, but the connection was not in a state that was valid for sending data. Based on the DTCSTM126I message, I would assume the connection was in the process of closing when the telnet server tried the send. Determining what was causing the connection to close would require some tracing either on the client side or on the TCP/IP stack (MORETRACE TCP would probably be the most enlightening from the stack point of view).
Regards, Miguel Delapaz z/VM Development The IBM z/VM Operating System <IBMVM@LISTSERV.UARK.EDU> wrote on 07/28/2009 12:02:13 PM: > We have been getting the messages > > 17:16:49 DTCSTM025I Telnet server: Conn 100: SendOutData (StMaster) > calls StKillConn in otherwise clause. > 17:16:49 DTCSTM028I Cannot send data > 17:16:49 DTCSTM126I Telnet server: Conn 100: StKillConn- TcpClose > failed: No such connection > > They appear to be associated, it is difficult to tell whether it is > before the fact or after it, with terminal sessions being dropped > with a lightning bolt 510 or just an x-clock. > > Unfortunately, the messages appear to be among those whose meaning > is "self-evident"; perhaps they are to the TCP/IP developers, but > not to me. How do I find out what is happening and how to avoid it? > > Regards, > Richard Schuh > > >
