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

Chapter 6 137
Troubleshooting the APPC Subsystem
Startup Problems
2. 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.