Browse Prior Art Database

LEN End Node Support of BIND Request Routing

IP.com Disclosure Number: IPCOM000113355D
Original Publication Date: 1994-Aug-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 40K

Publishing Venue

IBM

Related People

Brodd, JL: AUTHOR [+2]

Abstract

Disclosed is a method that allows a Low Entry Networking (LEN) End Node to know the Systems Network Architecture (SNA) Logical Unit (LU) names of attached intelligent workstations (IWS) without requiring pre-configuration of the IWS LU names in the LEN End Node. This allows BIND requests to be routed by the LEN End Node to the IWS.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 80% of the total text.

LEN End Node Support of BIND Request Routing

      Disclosed is a method that allows a Low Entry Networking (LEN)
End Node to know the Systems Network Architecture (SNA) Logical Unit
(LU) names of attached intelligent workstations (IWS) without
requiring pre-configuration of the IWS LU names in the LEN End Node.
This allows BIND requests to be routed by the LEN End Node to the
IWS.

      Before a BIND request can be routed by a LEN End Node to an
attached IWS, the LEN End Node must know the network qualified LU
name of the IWS.  The LEN End Node will require that the network
qualified LU name of each IWS be the same as the network qualified
Control Point (CP) name of the IWS.  This naming convention must be
followed for each IWS that will have BIND requests routed to it by
the LEN End Node.  The network qualified CP name is sent to the LEN
End Node by the IWS in the XID3 when the communication link between
the LEN End Node and the IWS is started.  The LEN End Node saves the
network qualified CP name for all attached IWSs and compares it
against the secondary LU name in BIND requests received from the
communications network.  If a match is found, the BIND request is
routed to the appropriate IWS.

      In addition, in order to support the routing of BIND requests
to multiple LUs within a single IWS, the LEN End Node will assume
that the IWS LU name(s) will either be exactly equal to the network
qualified CP name, or they will be equal to the network qualif...