HP-UX SNAplus2 Diagnostics Guide

Using Logging and Tracing
Tracing
Chapter 396
trace file. Each individual message is preceded by a horizontal line
indicating the time the trace entry was made.
• The process ID of the process being traced appears at the start of each
line. The process ID is followed by an indicator of the interface being
traced (for example, FMI).
• Message data is shown in the following formats in separate columns
to ensure that a character string in the message data appears as
readable text in either the EBCDIC or the ASCII column according to
its character set:
— Hexadecimal
— Interpreted as EBCDIC
— Interpreted as ASCII
Tracing for 3270 and RJE includes FMI DATA messages, which show the
data being transferred between the program and the host, and other
messages that are internal to SNAplus2. The start of each trace entry
shows the type of message being traced and a decoded version of some of
the header information. The header information and message data is
then traced.
This trace is provided mainly for use by SNAplus2 support personnel,
who may ask you to provide trace files to assist them in diagnosing
problems with the SNAplus2 system. It has the advantage of only
tracing a single program without impacting the performance of the
server.
Internal Tracing
Internal tracing traces data flow between SNAplus2 processes (the local
node and connectivity components). For an illustration of the overall
structure of SNAplus2 and the types of internal tracing you can specify
using the snapadmin set_trace_type command, see “Tracing
Interfaces”. The following section explains how to perform internal
tracing using the Motif administration program and the command-line
administration program.
Internal tracing is very verbose, and will usually only be used by
SNAplus2 support personnel.