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

37x5 to FEP-4600 Migration and Planning Guide
707117-003 7-7
VTAM Gen Requirements
Because the FEP-4600 spoofs the remote network resources to appear as though they
reside in the local network, the basic VTAM CTC definitions are no different than they
would be for the FEP-4600 used for a local PU 4 connection, or any normal CTC link to
another VTAM.
The VTAM gen requirements for a PU 4/SNI connection through the FEP-4600 are much
simpler than for a real 37x5. This is because VTAM sees the connection as a Channel-to-
Channel connection to an adjacent VTAM and the majority of the configuration will take
place on the FEP-4600 itself. You should define one Local SNA Major Node definition
(Link Station) for each path to a remote 3745 that you need to define. This includes
multiple paths to the same remote 3745. (You can use a single Local SNA Major Node
definition to define multiple connections (Link Stations), but you will then need to take
all of those connections down any time that you make a change to one of them.)
An example definition for a PU 4/SNI platform communicating through the FEP-4600
might look like this:
VISBLD VBUILD TYPE=CA
VISGRP GROUP LNCTL=CTCA,ISTATUS=ACTIVE,REPLYTO=25,MIH=YES
VISLN LINE ADDRESS=C30,MAXBFRU=16
VISPU1 PU PUTYPE=4,TGN=2
VTAM PATH Table Considerations
Because the FEP-4600 makes the remote FEP to FEP connections transparent to the
ESCON or FICON connections, the local PATH statements may need to be modified to
reflect the new apparent adjacent subarea if any have been defined. All resources that
were previously described as being on a foreign network must now appear to be on the
local network, residing in one of the subareas assigned to the FEP-4600. The FEP-4600
requires a separate subarea assignment for each remote SNI network connection that is to
be supported (only adjacent SNI networks). This will cause the GWPATH statements to
go away in the CDRM and be replaced by PATH statements in the PATH table. Note that
if the FEP-4600 is using the same subarea number as the 37x5 that it is replacing (only
one SNI connection), the PATH statement may already be defined. You may need to add
an explicit route to address a new TGN assignment defined for use by the FEP-4600.
PATH for Example 1:
Following is an example of the changes that would need to be made to the PATH table of
the VTAM that is directly adjacent to the FEP-4600. Reference the Before and After
diagrams found earlier in this chapter.
VTAM PATH Statements for VTAM 03 (Before)
PATH0302 PATH
DESTSA=02,ER0=(01,1),VR1=1
PATH0301 PATH DESTSA=01,ER0=(01,1),VR1=1
PATH0304 PATH DESTSA=04,ER0=(04,1),VR1=1