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

72 Chapter4
APPC Subsystem Configuration
Data Required From the Remote Configuration
Data Required From the Remote
Configuration
Data in the APPC subsystem configuration must correspond to
information from the remote configuration. Before using NMMGR, you
should consult with the remote system programmer to ensure that the
information in the following tables is consistent between the HP 3000
configuration and the remote system configuration.
If you are configuring the HP 3000 as a Node Type 2.0 that
communicates with a Type 5 (host) node, Table 4-1 lists the local and
remote configuration items that must agree.
NOTE Some sites use separate copies of the same application subsystem to
accommodate different types of users. For example, you may be given
one VTAM Appl ID for CICS to use for development sessions, and
another to user for run-time sessions.
You should also obtain the following items from the IBM host
programmer:
• The LINEID for each link you have to a remote system.
• The STARTED_TASK_NAME for each application subsystem you will
use.
Table 4-1 NCP, VTAN, and CICS Corresponding Values
Remote Configuration Item Field in NMMGR Screen NMMGR Screen
puname operand of PU macro SNA Node Name
APPC: Dependent LU
Session Type Data
luname operand of LU macro Local LU Names
APPC: Dependent LU List
Data
APPLID of Label field of the
VTAM APPL definition statement
Remote LU Name
APPC: Dependent LU
Session Type Data
CICS MODENAME operand of
DFHTCT TYPE=SYSTEM macro
Mode Name
APPC: Dependent LU
Session Type Data
RUSIZES parameter of MODEENT
Logmode Table macro
Maximum RU Size (Send)
and Receive)
APPC: Mode Type Data
SRCVPAC parameter of MODEENT
Logmode Table macro
Maximum Pacing Value
(Send)
APPC: Mode Type Data
SSNDPAC parameter of MODEENT
Logmode Table macro
Maximum Pacing Value
(Receive)
APPC: Mode Type Data