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

Chapter 2. Support of PU 2.0 Platforms
2-16 707117-003
Example Switched Major Node Definition:
SMN01 VBUILD TYPE=SWNET,
SWPU01 PU DLOGMODE=STUNSPEC,
MODETAB=SYSTSTMT,
USSTAB=USSTABA,
PUTYPE=2,
IDBLK=017, (3174 Compatible Controller)
IDNUM=86392, (Hex Value, Must Be Unique)
MAXOUT=7
WER002 LU
LOCADDR=2
WER003 LU LOCADDR=3
WER004 LU LOCADDR=4
WER005 LU LOCADDR=5,
DLOGMOD=SCS
SAP Usage with XCA Upstream Connections
Multiple XCA definitions are created to support the following scenarios:
 SNA PU2 traffic flow to multiple VTAMs
 To increase the capacity of traffic to the same VTAM
 To provide multiple paths to the same VTAM (through multiple ESCON
interfaces).
Connections are directed to the multiple XCA connections through use of the SAP
(Service Access Point) in the FEP-4600’s configuration. Multiple paths to the same
VTAM typically make use of the same SAP value. Paths to different VTAMs typically
make use of different SAP numbers.
Local Major Nodes and XIDs
Local SNA Major Node definitions do not allow you to define the IDBLK and IDNUM
parameters. When replacing a Switched Major Node definition or creating a new one
with a Local SNA Major Node definition, it will be necessary to configure the XID
information into the FEP-4600 configuration. This information is associated with the
subchannel address that is to be used to support this specific PU. A dynamic interface
will be configured on the FEP-4600, to receive the incoming connection. When the XID
is received from the incoming connection, the FEP-4600 will map the connection to the
appropriate upstream host connection.
Note that multiple dynamic interfaces may be configured on the FEP-4600 platform to
receive connections to the same host connection, allowing for load balancing and disaster
recovery.