SNA NRJE Node Managers Guide (30292-90007)

Chapter 5 79
SNA NRJE Troubleshooting
Submitting an SR
SNA Transport Information
For problems that might involve SNA Transport, see the SNA Link
Services Reference Manual or the SNA Link/XL Node Manager’s Guide,
keeping this in mind:
• For NRJE/V, when using the MPE command ABORTIO
ldev to try to
free an SNA Transport hang,
ldev specifies the INP being used.
Communications Link Information
For problems that might involve the communications link, see the SNA
Link Services Reference Manual or the SNA Link/XL Node Manager’s
Guide, keeping these things in mind:
• If you are running NRJE/V, an INP (instead of PSI) failure is a
possible problem. If this happens, give the file INPLOG
xx .PUB.SYS
(where
xx is a number from 00 through 99) to your HP
representative for additional analysis.
• If you are running NRJE/V and an INP failure has not occurred,
turn the trace on with the LINKCONTROL TRACEON MPE command.
SNA NRJE Information
For problems related to SNA NRJE, collect this additional information
to help your HP representative determine the cause and to solve your
problems:
• Supply copies of the output produced by the SNA NRJE DISPLAY
and STATUS commands. This output gives information about the
workstation and LUs.
• If an NRJE LU terminates abnormally with message #9074,
LU ABNORMAL TERMINATION. STACK DUMPED TO STDLIST.
obtain the printout from $STDLIST of the NRJE monitor process
(NRJEMON).
• If an LU hangs, you can force the LU to dump its stack to an output
spool file on device “LP” by issuing the NRJE command
DUMPLU;LU= LUName
• Examine the status of the SNA NRJE remote workstation at a host
operator’s console. For example, for a JES2 host you would issue the
command
$DU,RMT xx
where xx is the remote workstation number, or its equivalent, for
your job entry subsystem. Make a copy of this information for your
HP representative.