SNA Link/iX Node Managers Guide (30291-90507)

Chapter 5 135
SNA Link Troubleshooting
Problem Resolution
and this trace file to your Hewlett-Packard support contact for
analysis.
NOTE It is important to give a copy of the PSI dump that took place while
link-level tracing was enabled to your Hewlett-Packard support contact
for analysis.
• If a PSI failure has not taken place, turn on link-level tracing with
the MPE command SNACONTROL START or SNACONTROL TRACEON (see
Chapter 6 , “MPE Commands,” of this manual). This allows your
Hewlett-Packard support contact to study the line activity.
• If link trace logging is enabled, use the SWITCHLOG command to close
the current system log file (LOG
nnnn .PUB.SYS, where nnnn is a
number from 0000 through 9999) and open a new one. Then, give a
copy of the system log file you just closed to your Hewlett-Packard
support contact to analyze.
• If link trace logging is not enabled, enable it through NMMGR so
that the information will be available if the problem can be
reproduced.
X.25 Communications Link Information
For problems that involve the X.25 communications link, include this
additional information where applicable:
• If a fatal X.25 link error has occurred, messages in these formats
might be logged:
Link connect failure on node NodeName
Subsystem=SubsysID, Error Code=ErrorCode
Link failure, shutting down the node NodeName
subsystem=SubsysID, procedure=ProcNum, error num=ErrorNum
SOCKERR nnn
Link failure, shutting down the node NodeName
subsystem=SubsysID, procedure=ProcNum, error num=ErrorNum
Be sure to include these error messages in the CR exactly as they
appear on the operator’s console.