 |
» |
|
|
|
This section gives some suggestions for troubleshooting startup problems.
It is divided into two sections: Link and Node Level Problems
Check that the recommended logging classes have been enabled
at the system console through NMMGR. See the SNA Link/XL
Node Manager's Guide for Hewlett-Packard's
recommended logging configuration. Link and Node Level Problems | |
To determine whether the link and node have activated, issue
the SNACONTROL STATUS command, described in the SNA Link/XL Node Manager's
Guide. To check the status of a Type 2.1 node, use the LINK=LINKSTATE parameter to the SNACONTROL STATUS command. If the display does not say CONNECTED LEVEL 2, the node did not activate. This section describes some troubleshooting procedures to
be used when the SNA link does not activate properly. The SNA
Link/XL Node Manager's Guide contains more
detailed instructions for troubleshooting the SNA link product. | | | |  | NOTE: The APPCCONTROL START command will not activate the SNA node. To activate the
SNA node, issue the SNACONTROL START command, described in the SNA Link/XL Node
Manager's Guide. | | | | |
Validate the configuration file.
The NMMGR validation utility cross checks references to SNA nodes
and LUs to ensure that they are configured consistently between
the SNANODE and APPC branches of NMMGR. The NMMGR validation utility
is documented in Using the Node Management Services Utilities. Verify that the HP 3000 has been configured
properly. Check the following items: One PU per PSI.
When you run multiple PUs concurrently, each PSI requires a unique
PU and each PU requires a unique PSI. Configuration file name.
You must name the configuration file NMCONFIG.PUB.SYS. Consistent LU Names, SNA Node Name.
The LUs you configure for use by the APPC subsystem must also be
configured in the SNANODE branch of NMMGR. Make sure the LUs you configure
for the APPC subsystem are configured on the same 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.
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. | | | | |
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.
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. Check for hardware problems. Check that all hardware
is installed properly and working correctly. Make sure that the
proper cabling has been installed and connected and that the modems
are turned on and working properly. Many problems are related to
such things as incompatible modems, bad phone lines and cables and
so forth. Check for activity on the line. Make sure the line
is active (being polled) and the remote system's teleprocessing
subsystem (for example, VTAM) is active. You might need to use a
line monitor to determine whether the line is being polled and to
determine the addresses being polled. The standard HP line monitor
(HP 4953 or 4951) with the SDLC package can be used. If a PSI failure has occurred, give the file NETDMPxx.PUB.SYS (xx can equal 00 through 99) to your HP representative
for analysis. If you have thoroughly checked out all installation
and configuration items, and the HP 3000 link still does
not activate, perform a link level trace. Link level tracing is
described in the SNA Link/XL Node Manager's
Guide. When the problem has been reproduced, turn off link
level tracing, and give the trace file to your HP representative
for analysis. Print a copy of the output from the NMMAINT program
to record the software versions, and give this to your HP representative. If data is being received on the link, but the node
is not starting up, examine the SNA Transport node trace. The node
trace can be enabled at startup with the SNACONTROL START command. For more information, see the SNA
Link/XL Node Manager's Guide.
APPC Subsystem Problems | |
To determine whether the APPC subsystem has activated properly, issue
the APPCCONTROL STATUS command, described in Chapter 2 “Interactive Control Operator Commands” of
this manual. The Number of Active Sessions listed in the APPCCONTROL STATUS display should be equal to the Automatically Activated Sessions value for each configured session type. This section
describes some troubleshooting procedures to be used when the APPC
subsystem does not activate properly. Validate the configuration file. The
NMMGR validation utility cross checks references to SNA nodes and
LUs to ensure that they are configured consistently between the
SNANODE and APPC branches of NMMGR. The NMMGR validation utility
is documented in Using the Node Management Services Utilities. Verify that the HP 3000 has been configured
properly. Check the following items: LU session types. Make
sure the independent LU session types are configured to use independent
LUs on Type 2.1 nodes. Make sure the dependent LU session types
are configured to use dependent LUs on Type 2.0 nodes or on Type
2.1 nodes with dependent LU support. Local LU Name of independent LU. The
Local LU Name field of the "APPC: Independent LU Session
Type Data" screen must match the RMTLOCNAME in the Device Description on the AS/400. Fully Qualified Remote LU Name. The
Fully Qualified Remote LU Name field of the "APPC: Independent LU Session Type
Data" screen must be specified as RemoteNetID.RemoteLUName, where RemoteNetID matches the Local network ID in the Network Attributes Table on the AS/400,
and RemoteLUName matches the LCLLOCNAME in the Device Description on the AS/400. Mode name. Make sure the
mode name configured for the local LUs matches the mode name for
the remote LUs with which they will communicate. On an IBM mainframe,
a mode name is associated with an LU in the CICS MODENAME operand of the DFHTCT TYPE=SYSTEM macro. On an AS/400, a mode name is associated
with a device in the MODE field of the Device Description. Make sure any mode name you specify in the "APPC: Independent
LU Session Type Data" screen or the "APPC: Dependent
LU Session Type Data" screen is also configured in the "APPC:
Select Mode Type" and "APPC: Mode Type Data" screens
(unless you are using MODE0, which is internally defined). Parallel Sessions. If a device
on the AS/400 is configured to conduct a single session (
SNGSSN in the Device Description is *YES), make sure the Parallel Sessions field of the "APPC: Independent LU Session
Type Data" screen is set to N. If a device on the AS/400 is configured to conduct
parallel sessions (SNGSSN in the Device Description is *NO), make sure the Parallel Sessions field of the "APPC: Independent LU Session Type
Data" screen is set to Y. Unsolicited BINDs. Hewlett-Packard
recommends that you configure Unsolicited Binds = N in the "APPC: Dependent LU Session Type
Data" screen. If you configure Unsolicited Binds = Y, the HP 3000 will not send an INIT_SELF
request to initiate a session. It will simply wait for a BIND from
the host. If you specify Unsolicited Binds = Y, the CICS configuration on the host must specify
AUTOCONNECT = Y for the remote LU.
If the HP 3000 is configured to communicate
with an AS/400, make sure the LCLCTLSSN value is 0 in the Mode Description on the AS/400.
Make sure the LCLCTLSSN value is *NO in the Device Descriptions for all AS/400 LUs
that will communicate with the HP 3000.
If you have checked your configuration, and the APPC sessions
still do not activate, collect the SNA Transport user interface
trace and the APPC subsystem internal trace, and give them to your
HP representative for analysis. For instruction on turning on APPC subsystem
internal tracing, see the description of the APPCCONTROL START command, in Chapter 2 “Interactive Control Operator Commands” of this manual.
For instructions on turning on SNA Transport tracing, see the
SNA Link/XL Node Manager's Guide. |
