Materials needed to report Telnet problems

This topic lists the information that you might need to provide to your service representative when you report a Telnet problem.

Problems reported to IBM^® might include one or more in the following list as determined by your service representative:

Telnet Server job logs:
- QTVTELNET job log
- QTVDEVICE job log
Some details on the problem scenario. For example:
- The type of remote host you were using to Telnet from or to, such as an iSeries™, zSeries^®, or pSeries^® server. This is particularly useful if you are doing cascaded Telnet functions.
- The type of client attempting to connect to the Telnet server, such as IBM Personal Communications and iSeries Access for Windows^®.
The job log of the interactive job running Telnet client (when Telnet client is under investigation).
The trace job (TRCJOB) output of the failing interactive job (especially important if running Telnet client).
Note: Use TRCJOB *ON to start this trace. The result is a QPSRVTRC spooled file in the interactive job.
A communications trace of the failure, formatted for both ASCII and EBCDIC, which contains TCP/IP data only. Your service representative can direct you to include broadcast messages in this trace. In addition, you might need to filter this trace on a specific IP address if you have a large amount of traffic on your network, and know the IP address of the failing client.
Any licensed internal code (LIC) logs with major code 0700 and minor code 005x from the time of failure. In addition, there might be some major code 0701, and minor code 005x informational LIC logs that might be useful but not necessarily critical.
A Virtual Terminal Manager (VTM) LIC component trace. You can gather this trace using the trace TCP/IP application TRCTCPAPP command, or through the start system service tools(STRSST) command. For full details on using the trace TCP/IP application(TRCTCPAPP) command, see the TRCTCPAPP command description.

You will have performance impacts when you run the VTM LIC trace. Some examples of using this command are:

To trace all VTM activity:
```
TRCTCPAPP APP(*TELNET) SET(*ON)
```
To trace the activity on a specific device, when you know the device name:
```
TRCTCPAPP APP(*TELNET) SET(*ON) DEVD(devicename)
```
To trace the activity on a specific device, when you know the IP address of the client:
```
TRCTCPAPP APP(*TELNET) SET(*ON) RMTNETADR(*INET'www.xxx.yyy.zzz')
```
To turn the trace off and spooled file output:
```
TRCTCPAPP APP(*TELNET) SET(*OFF) 
```
Note: You should receive specific details of which trace parameters to use for your problem from your service representative before running this command. This ensures that you gather the correct information for your problem.