You need to plan how you want to configure the EE network before you start configuring.

Take the following steps to plan how to configure the EE network:

1. Draw a logical picture of your network and decide what types of EE connectivity you want to implement. Four choices are represented in Figure 1.
   • Host-to-host with same NETID

     This type of EE connection is between z/OS® hosts within your data center.

   • Host-to-host with extended border node to vendor

     This type of EE connection uses EE along with VTAM® extended border node to connect two vendors, replacing existing SNI connectivity.

   • Host-to-branch

     This type of EE connection sets a path to one or more branches across a WAN. This connection requires an EE-capable access point in the branch such as IBM® Communications Server for Linux on Intel or PCOMM.

   • HiperSockets™ within a CEC

     This type of EE connection is made between LPARs within a CEC.

   Figure 1. Four types of EE connectivity

   
2. Decide on the level of control, flexibility, and ease of use you need, and a naming scheme. See Types of definitions.
3. Review the following terms:

   model major node

   Defines a model PU to be used for dynamically created EE PUs on inbound connections.

   switched major node

   Defines the switched TGs with the following statements:

   • The PU statement defines the remote node.
   • The PATH statement defines the remote IPv4 address, or a host name that can be resolved into an IPv4 or an IPv6 address.

   XCA major node

   Defines the IP port with the following statements:

   • The PORT statement identifies the name of a port through which an HPR connection through the IP network is made. The PORT statement must be set to MEDIUM=HPRIP for EE.
   • One or more GROUP statements define a set of lines and PUs that represent potential EE partners. All lines and PUs under a given group are associated with a particular local IP address or host name.

4. Decide what types of EE connectivity you want to implement. All four types have these benefits:
   • Increased bandwidth because EE can use OSA Express® adapters.
   • Elimination of dependency on SNA legacy hardware such as the 3745 and ESCON-based channel connectivity.

   In addition, for host-to-host with EBN, another benefit is the elimination of Gateway NCP definitions. With HiperSockets, EE provides SNA applications with the ability to communicate across a high-speed low-latency data communication path, with no network connection and no special hardware.