APPC Subsystem on MPE/XL Node Manager's Guide (30294-90007)
228 AppendixC
Configuration Worksheets
Completing the Worksheets
Completing the Worksheets
This section gives you step-by-step instructions for filling out the
Independent LU Session Types worksheet, the Dependent LU Session
Types worksheet, and the Mode Types worksheet. One copy of each
worksheet is included at the end of this appendix. Make some
photocopies of the worksheets before you start filling them out so that
you will have enough room to plan your whole configuration.
Completing the Independent LU Session Types
Worksheet
An independent LU session type is used to communicate with an
independent LU on a peer (Type 2.1) node. Follow these steps to
complete the Independent LU Session Types worksheet:
1. Write the name of each independent remote LU with which you will
communicate in a separate Remote LU Name field on the worksheet.
For AS/400 communication, the Remote LU Name must match the
LCLLOCNAME in the Device Description on the AS/400.
The number of independent remote LUs you write down is the
minimum number of independent LU session types you will need.
(You might want to configure additional session types for reserved
sessions.)
2. Write a name for each independent LU session type in the Session
Type Name field next to each Remote LU Name. A Session Type
Name must be 8 or fewer characters long and begin with a letter. It
does not have to match anything in the remote configuration. Every
Session Type Name must be unique.
3. In the Remote Network ID field under each Remote LU Name,
write the network ID of the network where the remote LU is located.
For AS/400 communication, the Remote Network ID must match
the Local network ID in the Network Attributes Table on the
AS/400.
The Remote Network ID and the Remote LU Name make up the
Fully Qualified Remote LU Name in the “APPC: Independent LU
Session Type Data” screen in NMMGR.
4. In the SNA Node Name field under each Session Type Name, write
the name of the configured local SNA node that connects the
HP 3000 with the system where the remote LU is located. The SNA
Node Name, and the names of all the LUs associated with it, must be
already configured in the SNANODE branch of NMMGR.