HP-UX SNAplus2 Diagnostics Guide

Overview of Problem Solving
Types of Diagnostic Information
Chapter 126
Use client-server tracing to trace messages flowing
between the SNAplus2 server and a client, as well as
between SNAplus2 servers in the same domain.
Client-server tracing can be used, for example, to find
out why a client is unable to connect to the server.
Client-server tracing is written to text files. For more
information, see “Client-Server Tracing”.
TN server tracing
Use TN server tracing to record messages flowing
between the SNAplus2 TN server and its TN3270
clients. Typically, the System Administrator initiates
this trace to resolve a TN3270-related problem.
The TN server trace data is written to text files. For
more information, see “TN Server Tracing”.
3270 emulation program tracing and RJE workstation tracing
Use 3270 emulation program tracing and RJE
workstation tracing to show the data being transferred
between the program and the host, and messages that
are internal to SNAplus2. You control this tracing by
setting environment variables on the command line.
Trace data from the 3270 emulation program and RJE
workstation program is written to text files. For more
information, see “3270 Emulation Program Tracing
and RJE Workstation Tracing”.
Internal tracing
Use internal tracing to trace messages that flow
between internal components of the SNAplus2 node.
A large amount of trace output will usually be
generated quickly. Once you have captured the
information you need to solve your problem, stop
tracing to prevent files from growing too large or from
being overwritten. For more information about internal
tracing, see “Internal Tracing”.
The output produced by internal tracing (which is
typically used by support personnel) is binary. You can