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

Chapter 6 139
Troubleshooting the APPC Subsystem
Run-Time Problems
Run-Time Problems
This section gives some suggestions for troubleshooting run-time
problems. It is divided into the following sections:
• Lost Data
• APPC Subsystem Hang
• APPC Subsystem Failure
• Transaction Program Hang
• Remotely Initiated TP Failure
• System Hang or Failure
Lost Data
If data loss occurs at either the HP 3000 side or the remote side, follow
these steps:
1. Get a description of what is missing. Get copies of the original
document or file sent and the document or file that was received with
data missing.
2. Use a protocol analyzer to determine whether data is being
transferred.
3. If you suspect that the HP 3000 is causing the data loss, collect the
following things and send them to your HP representative for
analysis:
• the SNA Transport user trace (see the SNA Link/XL Node
Manager’s Guide)
• copies of the document or file sent and the document or file
received with data missing
• the APPC subsystem internal trace
• the NMMAINT.PUB.SYS version stamp
APPC Subsystem Hang
After you issue the APPCCONTROL STOP command to stop the APPC
subsystem (or after a TP calls the APPCStop intrinsic), the message
APPC: Subsystem Stopped (APPCLOG 1) should be logged to the
console screen. Issue the APPCCONTROL STATUS command to make sure
the subsystem has shut down completely. The APPCCONTROL STATUS
display will list any APPC sessions or transaction programs that are
still active after the APPCCONTROL STOP command has executed.