Visara FEP-4600 Planning Guide - Manual (Page 38)

Chapter 3. Support of PU 2.1 Nodes
3-2 707117-003
PU2.1 Gateway Operation
Two different approaches are offered on the host side for defining the downstream PUs to
VTAM.
The two options are partly dependent upon the network architecture of the downstream
PU, partly on the ESCON interface used, and partly on redundancy requirements.
Option 1: Define Local (Channel) Major Nodes for each remote PU2. (This option is only
supported over ESCON using the older Luminex ESCON card – no longer available, and
is not supported over FICON.)
Option 2: Define an XCA Major Node and use Switch Major Node definitions for each
PU2 (supported over ESCON and FICON).
Option 1 Considerations
This option is only available on older platforms that used the Luminex ESCON interface
card, and is not available on current platforms using the BARR ESCON interface card or
over FICON. When defining a Local Major Node definition for the FEP-4600, the
downstream PUs appear to VTAM as if they were physically attached to the ESCON
interface. This option is available if the PU is to be attached to the FEP-4600 via an
SDLC, Token Ring, or Ethernet (LLC) link. Defining Local Major Node PU 2.0
definitions requires one subchannel per PU.
Each PU 2.1 platform must be genned according to the function of the APPN node.
Network Nodes (NN), End Nodes (EN), and Low Entry End Nodes (LEN) are all
supported. All APPN nodes that must have an exclusive connection through the FEP-
4600 to VTAM, will require a definition. In the diagram below, three APPN (PU 2.1)
nodes will use the FEP-4600 to provide the connection to VTAM and all must have a
definition to VTAM and in the IO gen.
Configuration for the downstream media is performed in the FEP-4600 configuration. For
detailed configuration information, see the FEP-4600 Installation and Configuration
Guide.