HP-UX SNAplus2 Diagnostics Guide

Overview of Problem Solving
Types of Diagnostic Information
Chapter 1 25
The following section briefly describes the types of tracing and provides
examples of when to use tracing. For detailed information about tracing,
see “Tracing”.
Types of Tracing
SNAplus2 provides the following types of tracing:
Line tracing
Use line tracing to trace messages between the node
and the remote system. You can control the amount of
tracing by specifying the resource type (DLC, port, link
station, or session). Line Tracing is also sometimes
known as “DLC Tracing”.
Line tracing output is typically used by an SNA
administrator to solve end-user problems, including
the inability to bring up a session or session failure.
The format is a standard SNA trace. For more
information about line tracing, see “Line Tracing”.
The output produced by line tracing is binary. You can
select specific entries from a line trace file by using the
snapfilter utility, and you can format binary trace
output into text files by using the snaptrcfmt utility.
For more information about these utilities, see
Appendix A, “Using snapfilter and snaptrcfmt.”
API tracing
Use API tracing to locate communication problems that
involve any of the following SNAplus2 APIs: Advanced
Program-to-Program Communication (APPC),
Common Programming Interface for Communications
(CPI-C), Logical Unit Application (LUA), High Level
Language Application Program Interface
(HLLAPI),Node Operator Facility (NOF), Management
Services (MS), and Common Service Verbs (CSVs). API
tracing traces all the parameters supplied to the API
library or driver by an application and all the
parameters returned by the API library.
API trace data is written to text files. For more
information, see “API Tracing”.
Client-Server tracing