On Thursday, 01/05/2006 at 11:57 EST, Mark Bodenstein <[EMAIL PROTECTED]> wrote: > A correction to the story below: TCPIP did not stop working at any > time. It dealt gracefully with the full A disk. Also, I didn't have > to guess what happened; TCPIP announced it quite clearly in it's console: > > 05/12/23 08:56:29 TCPIP CORNELLC: DMSERD107S DISK A(191) IS FULL > 05/12/23 08:56:29 TCPIP CORNELLC: ERROR WRITING FILE "TCPIP > PROB0001 A1" ON DISK - OUTPUT HALTED
Whew! You made me nervous there for a minute.... > Our question is what caused normal TCPIP console output, specifically > telnet connection opened and closed messages, to go to the trace file > and not to the console? It is a side effect of the telnet server being imbedded in the stack. Telnet server messages go to the same place as as the stack's debug messages. Alan Altmark z/VM Development IBM Endicott
