Networking on z/OS
Previous topic | Next topic | Contents | Glossary | Contact z/OS | PDF


APPN databases

Networking on z/OS

APPN provides automatic network topology and directory support within APPN networks that simplifies network definition and permits dynamic selection of network routes. Some of the functions of APPN are topology and route selection services, and distributed directory searches.

APPN topology and route selection services

Topology and route selection services selects the best route to access a remote LU based on a set of user-specified criteria. Using the properties of the nodes and links in the network that are maintained in a network node topology database, a network node server calculates the best route from the local control point of the primary LU to the control point of the secondary LU according to the class of service selected by the LU initiating the session.

Topology and routing services is responsible for three functions:
  1. Maintaining the topology database
  2. Maintaining the LOGMODE-to-APPNCOS mapping table
  3. Calculating session routes based on (1) and (2).

Distributed directory searches

Distributed directory searches determine (through a network search) the current node location of any remote logical unit (LU) that is known locally only by name. This alleviates the need to define routing or location information for every remote LU with which a local LU can establish a session. The information collected during the directory search is stored in the network node's directory database.

You can compare the directory services database to a telephone book or address book, in which you look up a name (an LU's name) and determine its address.

An SNA session is the logical connection between two LUs. The LU that originates the session is named the originating LU (OLU), and its session partner is the destination LU (DLU). As its name implies, the originating LU initiates the session by sending a BIND to the destination LU.

The topology database is like a map, in which the APPN network nodes furnish the two addresses (the locations of the originating logical unit, OLU, and destination logical unit, DLU) and decide what the best route is between them based on your "driving requirements" (or "class of service"). That is, do you want to take the high speed route, the scenic route, or the most direct route? The BIND sent by the originating logical unit uses the best route that is available at the time the session is setup.





Copyright IBM Corporation 1990, 2010