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

Chapter 4 83

APPC Subsystem Conﬁguration

Conﬁguring the APPC Subsystem

An independent LU can communicate with another independent LU on

a Type 2.1 node, like an IBM AS/400. The APPC subsystem allows the

HP 3000 to act as a Type 2.1 node in a peer-to-peer environment, where

two independent LUs can establish an APPC session between

themselves without the supervision of the SSCP on a host node.

An independent LU can function as either a primary or a secondary LU;

that is, it can initiate an APPC session by sending a BIND to the

remote LU, or it can receive a BIND from the remote LU.

An independent LU on the HP 3000 can carry on multiple (parallel)

sessions with a remote independent LU. To allow parallel sessions with

the remote LU, enter Y in the Parallel Sessions ﬁeld of the “APPC:

Independent LU Session Type Data” screen.

An independent LU can communicate with several remote LUs at once;

however, all the remote LUs with which it communicates must be

connected to the HP 3000 through the same local SNA node (the same

copy of SNA/SDLC Link/XL). (To conﬁgure an independent LU to

communicate with multiple remote LUs, conﬁgure one session type for

each remote LU, and specify the same Local LU Name for each session

type.

If you want independent LU sessions with remote LUs that are

connected to the HP 3000 through different local SNA nodes, you must

conﬁgure a different local independent LU for each node.

Figure 4-7 Independent LU Session Type Data Screen