You can use the TCPIP DEBUG command to set specific debug options to monitor TCP/IP system activity.
The DEBUG command has two options: TRACE, which traces the data flow through the TCP/IP software, or DUMP, which enables you to examine the contents of various data structures. These options are described in more detail in the following subsections.
The DEBUG command enables you to specify the environment (MCP server, Windows server, or both) you want to examine or trace. The environments you can specify when running DEBUG are as follows:
-
All
The command applies to the MCP server and all Windows servers. This is the default.
-
MCP
The command applies only to the MCP server.
-
NP<#>
The command applies only to the Windows server specified.
| Note: | The DEBUG command reports diagnostic messages to the SUMLOG for internal use only. Examples of some diagnostic error messages include procedure entrance and exit tracing, internal data structure contents, and detection of error conditions. These messages are subject to change or deletion at any time during the lifetime of the TCP/IP product. The sole purpose of the DEBUG command is to provide additional diagnostic capabilities if a problem occurs. The output from this command should be forwarded to the TCP/IP engineering group along with a UCF for further analysis. Be aware that setting options of the DEBUG command could have an adverse effect on network performance. |
Trace Options and Dump Options identify the TCP/IP DEBUG command options that can be helpful when identifying the area preventing TCP/IP communication. For more information on this command, refer to the Networking Commands and Inquiries Help.
