HP-UX SNAplus2 Diagnostics Guide

Overview of Problem Solving
Types of Diagnostic Information
Chapter 1 27
select specific entries from an internal 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.”
Using Tracing
If you encounter a problem, use the SNAplus2 trace facilities to obtain
more information about the messages that are flowing across specific
interfaces. For example:
• If you have an application that uses the SNAplus2 APIs and the API
return codes indicate a problem, use API tracing.
• If you are unable to connect to a remote system successfully, or if
SNAplus2 produces exception and problem logs when you try to do so,
use line tracing or client-server tracing.
NOTE Do not run SNAplus2 tracing unless you have encountered a problem
with your SNAplus2 system. The system runs more slowly when tracing
is enabled.
For more information about using tracing, see “Tracing”, or refer to the
HP-UX SNAplus2 Administration Guide.
Alerts
Alerts are SNA messages that are generated automatically. They are
sent to and processed by different programs on the external network and
are used to identify problems or impending problems. There can be alerts
from connectivity components, 3270 user alerts, or alerts provided by an
application program using the Management Services API.
Alerts are sent to the first active host link encountered or to the link
station you specified using the snapadmin define_default_pu
command. If the link station is inactive, alerts are stored on disk and
transmitted when the link station is reactivated.
NetView, which typically runs on the host, is the most commonly used
program for viewing and processing alerts.