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

142 Chapter6
Troubleshooting the APPC Subsystem
Run-Time Problems
Remotely Initiated TP Failure
If a remotely initiated TP that worked on a previous version of APPC
fails after you install a new version, get a user trace of the TP and check
the status info value returned on the MCGetAllocate intrinsic.
If the status info value is -1008, do the following things:
1. Modify the local TP so that it passes the
LocalTPName as an input
parameter to the MCGetAllocate intrinsic.
On older versions of the APPC subsystem, the LocalTPName was an
output parameter. However, on the Node Type 2.1 version of the
APPC subsystem, the
LocalTPName is an input parameter.
2. Make sure the
LocalTPName parameter of the MCGetAllocate
intrinsic matches the
LocalTPName parameter of the TPStarted
intrinsic.
3. Use NMMGR to configure the LocalTPName as a remotely initiated
TP. See Chapter 4 , “APPC Subsystem Configuration,” in this
manual for more information.
System Hangs or Failures
In the event of a system hang or failure, perform the following steps:
1. Take a memory dump, format the dump and store off the spool file to
tape.
2. Store the following files off to tape and submit them, along with the
memory dump, to your HP representative for analysis.
• The APPC subsystem internal trace and the LU 6.2 product user
trace.
• The version stamps from running NMMAINT.PUB.SYS.
• The NMS log file (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.