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 “NCP, VTAN, and CICS Corresponding Values” lists the local and remote configuration items that
must agree.
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 |
 |
| |
|
 | 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.
Though these two items have no corollaries in the HP 3000 configuration,
you will need them when communicating with people at the remote
site.
If you are configuring the HP 3000 as a Node Type
2.1 that communicates with an AS/400 (Type 2.1 node), Table 4-2 “AS/400 Corresponding Values” lists the local and remote configuration items that
must agree.
|
| |
|
| NOTE: When you configure an IBM AS/400 to communicate with
the HP 3000, you must configure the HP 3000 controller
as an APPN-capable LEN node. |
|
| |
|
Table 4-2 AS/400 Corresponding Values
Remote Configuration Item | Field in NMMGR Screen | NMMGR Screen |
|---|
RMTLOCNAME of Device Description | Local LU Name | APPC: Independent LU Session Type Data |
RMTNETID of Controller Description (If RMTNETID = *NETATTR, use Local network ID of Network Attributes Table.) | Local Network ID | APPC: Network ID Data |
Local network ID of Network Attribute Table, and LCLLOCNAME of Device Description | Fully Qualified Remote LU Name | APPC: Independent LU Session Type Data |
MODE of Device Description | Mode Name | APPC: Independent LU Session Type Data |
MAXLENRU of Mode Description | Maximum RU Size (Send and Receive) | APPC: Mode Type Data |
INPACING of Mode Description | Maximum Pacing Value (Send) | APPC: Mode Type Data |
OUTPACING of Mode Description | Maximum Pacing Value (Receive) | APPC: Mode Type Data |
Because the APPC subsystem does not support remotely controlled sessions,
you must configure the following values on the AS/400:
For parallel sessions, the
Locally controlled sessions value in the Mode Description must be 0.
For single independent sessions, the Locally controlled session value in the Device Description must be NO.
