Example: Multiple iSeries systems using APPN

The following sections describe configuration for the network that is shown in Figure 8. In this network, seven iSeries systems are configured to communicate, using the APPN functions. Network attributes, line descriptions, APPC controller descriptions, and APPC device descriptions are created, either automatically or manually, to set up this network.

Figure 8. Multiple iSeries systems using APPN

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

New York

• Example: Configure end node 1 (New York)
• Change the network attributes (New York) in multiple-system network
• Create the remote location configuration list (New York)
• Create the line description (New York to Chicago)
• Create the controller description (New York to Chicago)
• Create the line description (New York to Minneapolis)
• Create the controller description (New York to Minneapolis)

Chicago

• Example: Configure network node 1 (Chicago)
• Change the network attributes (Chicago) in multiple-system network
• Create the line description (Chicago to New York)
• Create the controller description (Chicago to New York)
• Create the line description (Chicago to Minneapolis) in multiple-system network
• Create the controller description (Chicago to Minneapolis) in multiple-system network
• Create line description B (Chicago to Minneapolis) in multiple-system network
• Create controller description B (Chicago to Minneapolis) in multiple-system network

Minneapolis

• Example: Configure network node 2 (Minneapolis) in multiple-system network
• Change the network attributes (Minneapolis) in multiple-system network
• Create the line description (Minneapolis to New York, switched)
• Create the controller description (Minneapolis to New York, switched)
• Create the line description A (Minneapolis to Chicago)
• Create the controller description (Minneapolis to Chicago, nonswitched)
• Create the line description B (Minneapolis to Chicago)
• Create the controller description (Minneapolis to Chicago, switched)
• Create the line description (Minneapolis to Los Angeles, switched)
• Create the controller description (Minneapolis to Los Angeles, switched)
• Create the line description (Minneapolis to token-ring network)
• Create the controller description (Minneapolis to Purchasing, token-ring network)
• Create the controller description (Minneapolis to Distribution, token-ring network)
• Create the controller description (Minneapolis to Payroll, token-ring network)

Los Angeles

• Example: Configure end node 2 (Los Angeles)
• Change the network attributes (Los Angeles) in multiple-system network
• Create the line description (Los Angeles to Minneapolis)
• Create the controller description (Los Angeles to Minneapolis)

Purchasing

• Example: Configure end node A (Purchasing)
• Change the network attributes (Purchasing)
• Create the remote location configuration list (Purchasing)
• Create the line description (Purchasing to token-ring network)
• Create the controller description (Purchasing to Minneapolis, token-ring network)
• Create the controller description (Purchasing to Distribution, token-ring network)

Distribution

• Example: Configure end node B (Distribution)
• Change the network attributes (Distribution)
• Create the line description (Distribution to token-ring network)
• Create the controller description (Distribution to Minneapolis, token-ring network)
• Create the controller description (Distribution to Purchasing, token-ring network)

Payroll

• Example: Configure low entry networking end node 1 (Payroll)
• Create the line description (Payroll to token-ring network)
• Create the controller description (Payroll to token-ring network)
• Create the APPC device (Payroll to New York)
• Create the APPC device (Payroll to Los Angeles)
• Create the APPC device (Payroll to Minneapolis)