Sample configuration with a token-ring local area network

Figure 1 shows a multiple domain XCA configuration.

To be in session across the XCA connection, application programs in each VTAM® must be compatible application programs (that is, they must both be SNA applications programs).

To define the configuration in Figure 1, define the following in the VTAM connected through the IBM® 3172 Nways Interconnect Controller:

One external communication adapter major node to represent the physical unit in the IBM 3172 Nways Interconnect Controller. This physical unit is used for network management purposes. If you are running the NetView® program, it is recommended that you code this definition statement. By defining this physical unit, you can have the IBM 3172 Nways Interconnect Controller forward the same type of information that a 3174 cluster controller forwards. For example, any alerts detected by the IBM 3172 Nways Interconnect Controller would be forwarded.
One external communication adapter major node for each LAN connected to the IBM 3172 Nways Interconnect Controller.
Major nodes for any devices connected to the LAN.

Figure 1. XCA multiple domain configuration

Following is an example of coding used for the configuration in Figure 1 (VTAM attached through the 3172 Nways Interconnect Controller):

Define an external communication adapter major node to represent the physical unit in the IBM 3172 Nways Interconnect Controller:

XCACON1  VBUILD TYPE=XCA               XCA MAJOR NODE
PORT1    PORT  MEDIUM=BOXMGR,          3172 MANAGER
               CUADDR=500              CHANNEL UNIT ADDRESS
*
GROUP1   GROUP ISTATUS=ACTIVE          ACTIVATED AT GEN
LINE1    LINE
PU1      PU

Define another external communication adapter major node for the token ring:

XCACON2  VBUILD TYPE=XCA               XCA MAJOR NODE
PORT2    PORT  MEDIUM=RING,            TOKEN-RING
               SAPADDR=4,              SERVICE ACCESS POINT ADDRESS
               ADAPNO=1,               ADAPTER NUMBER
               CUADDR=BC0              CHANNEL UNIT ADDRESS
*
GROUP2A  GROUP DIAL=YES,               SWITCHED PERIPHERAL NODE
               ANSWER=ON,              DIAL WILL ACCEPT CALLS
               CALL=INOUT,             DIAL IN AND OUT
               ISTATUS=ACTIVE          ACTIVATED AT GEN
LINE2A   LINE  ANSWER=ON               PU CAN DIAL IN
PU2A     PU
*
GROUP2B  GROUP DIAL=NO                 NCP SUBAREA
               ISTATUS=ACTIVE          ACTIVATED AT GEN
LINE2B   LINE
PU2B     PU    MACADDR=400007777757,   LAN MEDIUM ACCESS CONTROL ADDRESS
               PUTYPE=4,               NCP PU
               SAPADDR=8,              SERVICE ACCESS POINT ADDRESS
               SUBAREA=22,             NCP'S SUBAREA NUMBER
               TGN=1                   TRANSMISSION GROUP NUMBER

Define a switched major node for the peripheral node attached to the LAN:

SWNODE1  VBUILD TYPE=SWNET
PU2      PU    DISCNT=YES,              DISCONNECT FACILITY
               DYNLU=YES,               DYNAMIC DEFINITION OF ILU (CDRSC)
               IDBLK=002,               BLOCK IDENTIFICATION
               IDNUM=000002             IDENTIFICATION NUMBER
               PUTYPE=2                 PHYSICAL UNIT TYPE
*
LANPATH2 PATH  DIALNO=0104000069010C59, TIC, SAP, MACADDR
               GRPNM=GROUP2A            LOGICAL GROUP DEFINITION
LU2      LU    LOCADDR=2,               DEPENDENT LU
               ISTATUS=INACTIVE         INITIAL STATUS INACTIVE

Notes:

You need to code one LINE and PU definition statement in the dial GROUP definition statement for every simultaneous peripheral node connection.
Switched devices connected to a LAN are defined to VTAM using the model major node. See Defining resources dynamically.
Multiple VTAM hosts can be in session with different stations on the LAN through one IBM 3172 Nways Interconnect Controller. To implement this support, code a different SAPADDR and MACADDR value combination to distinguish between the two hosts.