APPC Subsystem on MPE/XL Node Manager's Guide (30294-90007)

130 Chapter6
Troubleshooting the APPC Subsystem
Troubleshooting Tools
Troubleshooting Tools
This section describes the available troubleshooting tools and tells you
how to use them to troubleshoot the APPC subsystem. The tools
provided on the HP 3000 for troubleshooting the APPC subsystem are
as follows:
• the APPC subsystem internal trace
• APPC subsystem logging
• APPC subsystem messages and return codes
• the APPCCONTROL STATUS command
• the SNACONTROL STATUS command
NOTE User tracing is available for debugging transaction programs that call
LU 6.2 API intrinsics. User tracing is documented in the LU 6.2 API
Application Programmer’s Reference Manual.
APPC Internal Tracing
Internal tracing can be turned on at subsystem startup or during run
time. It traces the internal events of the APPC subsystem. Once the
trace has been turned on, it remains on until the APPC subsystem
shuts down or until you issue the APPCCONTROL TRACEOFF command.
At subsystem startup, internal tracing is turned off by default, but you
can turn tracing on when you issue the APPCCONTROL START command
by specifying TRACEON=YES. If you activate the APPC subsystem
programmatically, you can turn tracing on by setting the
TraceOn
parameter of the APPCStart intrinsic to 1.
During run time, you can turn internal tracing on by issuing the
APPCCONTROL TRACEON command.
NOTE Hewlett-Packard recommends that you turn on internal tracing when
you install an LU 6.2 product on your system for the first time.
It is not necessary for you to read and interpret the internal trace, but
you may be asked to collect it for analysis by your HP representative.
When you turn on APPC subsystem internal tracing, you can specify a
name for the trace file, or you can allow the trace file name to default.
The default trace file name is NMTC
xxxx .PUB.SYS, where xxxx is a
number from 0000 through 9999. This number is incremented
whenever a new trace file is created.