Warning: Be very careful what commands you issue via NETSTAT. Someone here accidentally issued NETSTAT OBEY CP Q TRACE.
This turned on a TCP/IP trace. This slowed down TCPIP so much that it rejected any logins or new NETSTAT commands; it also filled up the spooling space. (It also uncovered a problem with the backup system that we use to login when TCP/IP access is not available -- but that's another story.) IBM told us: When an OBEY command is issued the parser ignores any invalid keywords in the string but reads the entire string to the end. Unfortunately TRACE is a valid command, it turns on TRACE MOST by default. So ignoring the invalid keywords the command that got accepted was NETSTAT OBEY TRACE. The PROFILE TCPERROR file reported that to you. Development does not believe it is a bug the parser parsed the string as it was designed and supposed to do. I will open a development report to see if that can be visited in the next release and maybe changed. Development does not feel the change should be made via an APAR. So I thought I'd better warn everyone! Alan Ackerman alan (dot) ackerman (at) bank of america (dot) com
