Example: Three iSeries systems using APPN

In Figure 6, A and B are end nodes. The network node must configure its network attributes to reflect that it is a network node. Each system must configure the remote control-point name in the controller description that represents the adjacent system. Also, A and B must indicate in the controller description for the network node that it can be a network node. A and B must add the network node to the server list in network attributes so that the network node might act as a network server for both end nodes.

Figure 6. Three-system APPN network

Each list below represents a city within the network in Figure 6 above. See the links in each list to determine the configuration requirements for each system.

New York

• Example: Configure system A (New York)
• Change the network attributes (New York) in three-system network
• Create the remote location configuration list (New York) in three-system network
• Create the line description (SDLC nonswitched - New York)
• Create the controller description in three-system network (New York)

Los Angeles

• Example: Configure system B (Los Angeles)
• Change the network attributes (Los Angeles) in three-system network
• Create the remote location configuration list (Los Angeles)
• Create the line description (Los Angeles)
• Create the controller description (Los Angeles)

Chicago

• Example: Configure system C (Chicago)
• Change the network attributes (Chicago) in three-system network
• Create the line description (Chicago to New York) in three-system network
• Create the controller description (Chicago to New York) in three-system network
• Create the line description (Chicago to Los Angeles)
• Create the controller description (Chicago to Los Angeles)