The communications trace function lets you start or stop a trace of data on communications configuration objects. After you have run a trace of data, you can format the data for printing or viewing. You can view the printer file only in the output queue.
Communication trace options run under system service tools (SST). SST lets you use the configuration objects while communications trace is active. You can trace and format data for any of the communications types that you can use in a distributed database network.
You can run the iSeries™ communications trace from any display that is connected to the server. Anyone with a special authority (SPCAUT) of *SERVICE can run the trace on iSeries server. Communications trace supports all line speeds.
You should use communications trace in the following situations:
You must have detailed knowledge of the line protocols that you use to correctly interpret the data that is generated by a communications trace. For information about interpreting DRDA® data streams, see Example: Analyze the RW trace data.
Whenever possible, start the communications trace before varying on the lines. This gives you the most accurate sample of your line as it varies on.
To run an APPC trace and to work with its output, you have to know on what line, controller, and device you are running.
To format and avoid unwanted data in the output of a TCP/IP trace, you can specify the IP addresses of the source and application servers (ASs). Sometimes it is sufficient to just specify the port number instead, which is easier.
The following commands start, stop, print, and delete communications traces: