APPC Subsystem on MPE/XL Node Manager's Guide (30294-90007)
Chapter 6 141
Troubleshooting the APPC Subsystem
Run-Time Problems
2. Find the APPC dump if there is one. APPC dumps are created
automatically in certain cases. The following message should appear
on the console, containing the name of the dump file:
APPC: Object dumped to file APPCDP03 (APPCLOG 29).
The file will be called APPCDP
xx
.APPC.SYS where
xx
is a number
from 00 through 49. To be sure you collect the most recent file, store
off all files with the name APPCDP
xx
.
3. Collect the following information for analysis by your HP
representative:
• The user trace files and the APPC internal trace files.
• The version stamps from running NMMAINT.PUB.SYS.
• The NMS log file. The name will be NMLG
xxxx
.PUB.SYS. The
current log file will be locked, so issue the command
SWITCHNMLOG to close the current log file and start a new one.
4. Submit the data you collected to your HP representative for
analysis.
Transaction Program Hang
When a user reports a deadlocked or hung transaction program (a
program that does not return control to the user), the problem could be
caused by the program or by the APPC subsystem. Follow the
procedure below:
1. Record any messages the user received.
2. Check the error and logging messages.
3. Issue the APPCCONTROL STATUS command. If the subsystem is not
active, see “APPC Subsystem Failure,” earlier in this chapter. If the
subsystem is still active, find out which session the deadlocked TP is
using.
4. Try to bring down the session with the APPCCONTROL STOPSESSION
command. If the session does not come down, see “APPC Subsystem
Hang,” earlier in this chapter.