APPN end nodes implement a subset of the full APPN functions and rely on one of the network nodes they are attached to for accessing the network, locating resources, and providing routing services.

• All end nodes provide a peer environment for LU-LU (independent LUs) sessions where one LU resides in the local end node.
• The end node is limited in what it can do on its own. It requires the cooperation from an adjacent network node server with which the end node has established a CP-CP sessions. The adjacent network node server assists the end node in locating session partners, choosing session paths, and routing the bind to establish sessions.
• APPN end nodes also can register their local LUs and local topology (links to other network nodes and end nodes) to their network node server as well, thereby eliminating the need to send these EN transmission group vectors (TGVs) on every APPN locate request/reply. By reducing the number of searches sent to an EN, the EN can dedicate more of its resources (CPU, memory, and so on) to more productive work.
• End nodes do not participate in network topology exchange, but they do maintain their local topology.
• An APPN end node can have links to multiple nodes, including multiple network nodes, but may have CP-CP sessions with only one network node at a time (its network node server).
• Multiple attachment points between an end node and the APPN network may be desirable for increased throughput and high network availability. Attachment to multiple network nodes allows the end node to switch to a different network node server if its original network node server fails or connectivity to it is lost.
• An APPN end node can attach to any low-entry networking or APPN node.
• An end node is not required to have the same NETID as its network node server or any adjacent node.