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

Chapter 7. NULL SNI Networks
7-8 707117-003
VTAM PATH Statements for VTAM 03 (After)
PATH0302 PATH
DESTSA=02,ER0=(02,1),VR0=0
PATH0301 PATH DESTSA=01,ER0=(01,1),VR0=0
PATH0305 PATH DESTSA=05,ER0=(05,2),VR0=0
The primary change that occurred was that the reference to subarea 04 previously used by
NCP has been removed and replaced by a reference to SA05 used by the FEP-4600. The
TGN used by the FEP-4600 in Example 1 is ‘2’. Note that during testing periods, by
setting up a different subarea for the FEP-4600, it is possible to leave the PATH0304
definition in the table. It is generally not recommended to use the same subarea number
in the 3745 and FEP-4600 as this complicates the whole testing procedure.
PATH Example 2:
This example shows the FEP-4600 requirements for setting up parallel Transmission
Groups. For this example, use the diagram below. Because of the way the FEP-4600
supports PU 4 type connections, if you want to provide multiple connections between the
FEP-4600 and a remote NCP, you will need to set up parallel Transmission Groups on
both the ESCON or FICON side and the remote side. Remember that the FEP-4600 does
not currently support Multilink Transmission Groups. Note that depending upon the
desired results, you can define multiple TGs through the same physical ESCON/FICON
interface, and you can similarly define multiple TGs through the same LAN interface.
This however will continue to give you single points of failure, so you will probably want
to establish the multiple links through physically different interfaces. In this case you
would probably want to use the same subarea number (SA05) for both paths.
PROD1
VTAM
SA01
PROD2
VTAM
SA02
PROD3
Gateway
VTAM
SA03
CPU FEP-4600
CTC
3745 CPU
ACME1
Gateway
VTAM
SA10
CTC
Null Network
NETID=NULL
NETID=NET1
NETID=NET2
NET1 - SA05
NULL - SA98
GWNCP14
Gateway
NCP
NULL
SA99 NET1
SA14 TGN=1
TGN=2
TGN=7
CTC
TGN=3
TGN=8