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

Chapter 6 135
Troubleshooting the APPC Subsystem
Startup Problems
SNA node in the APPC subsystem configuration and the SNA
node configuration.
• Node Type 2.1. If the HP 3000 is configured to communicate
with a peer node, like an IBM AS/400, make sure the Node Type
in the “SNA Node Configuration: PU Data” screen is configured
as 2.1.
• ID BLK and ID NUM. If the HP 3000 is configured to
communicate with a peer node, like an IBM AS/400, make sure
the ID BLK and ID NUM, together, match the Exchange ID
configured on the remote system. This is for switched and
non-switched lines.
• LU numbers. For independent LUs, the LU# field of the “SNA
Node Configuration: LU Data” screen must be left blank.
3. For problems that may involve NMMGR or Node Management
Services, give your HP representative a copy of the forms file,
NMMGRF.PUB.SYS, and the configuration file, NMCONFIG.PUB.SYS.
With this information, your HP representative may be able to
determine whether the problem is related to the configuration of the
APPC subsystem or SNA Transport.
NOTE Certain values in the remote system configuration must match values
in the HP 3000 configuration file. See Chapter 4 , “APPC Subsystem
Configuration,” in this manual and the SNA Link/XL Node Manager’s
Guide for more information.
4. Verify the following items in the remote system configuration:
• Device configuration. Perhaps the remote system programmer
configured too many or the wrong type of device for a particular
line. If two LUs are configured, they should belong to a single PU.
• Incorrect macro definition. A macro could be missing a
required operand, or the host system programmer may have
specified an invalid operand for a particular macro.
For switched lines, the VBUILD macro should be in a separate
member in the VTAM parameter library (SYS1.VTAMLST).
• APPC LUs configured in the application subsystem. APPC
LUs may need to be configured in an application subsystem (such
as CICS) as well as in VTAM.
5. Check to see whether the remote LU is active. If the node is active,
but the APPCCONTROL STATUS command shows that the APPC
subsystem is not active, make sure that the host has activated the
line, the PU, and the LU. If you are communicating with an AS/400,
make sure the Line description, Controller description, and Device
description have been activated.