Tracing

If you cannot resolve a problem using the available tools, IBM® service will likely need a CTRACE with option Telnet. For details, see Telnet CTRACE. You might also need to activate one of the following additional traces:

• Full data trace

  If the problem is data related, use the FULLDATATRACE statement to trace all the data coming into and leaving Telnet rather than tracing only the first 64 bytes of data. FULLDATATRACE will cause a trace-wrap condition more quickly so it should be set only if needed. It should be set in PARMSGROUP instead of TELNETPARMS if a subset of clients can be identified.

• Telnet subagent trace

  For Telnet SNMP subagent problems, use the TNSATRACE keyword on the TNSACONFIG statement in PROFILE.TCPIP at startup. This will generate trace points throughout Telnet subagent processing, in addition to tracing data passed between the Telnet subagent, Telnet, and the TCP/IP stack. Subagent tracing can also be enabled after Telnet has been started by using the VARY TCPIP,tnproc,OBEYFILE command. To enable tracing using the VARY TCPIP,tnproc,OBEYFILE command, the subagent must first be disabled and then re-enabled with the TNSATRACE keyword. Trace data is written to the syslog daemon. Subagent tracing can be disabled using the NOTNSATRACE keyword.

• DBCS trace

  If the problem is with a DBCS connection, use the DBCSTRACE statement in the TELNETPARMS block or in the PARMSGROUP block to produce DBCS-specific trace entries in the SYSPRINT and TNDBCSER data sets.