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

37x5 to FEP-4600 Migration and Planning Guide
707117-003 4-3
On a processor that supports Logical Subsystems (such as the z990), the definitions will
look slightly different. Here is the same set of definitions as would be seen for the z990.
RESOURCE PARTITION=(CSS(0),(PROD1,1),(TEST,3))
CHPID PATH=(CSS(0),1E),TYPE=CNC,SWITCH=01,SHARED,PCHID=160
CNTLUNIT CUNUMBR=1E00,PATH=(CSS(0),1E),UNITADD=((00,1)),UNIT=3174,LINK=(CSS(0),C5)
IODEVICE CUNUMBR=1E00,ADDRESS=(1700,1)UNIT=3270-X,UNITADD=00,PARTITION=(CSS(0),PROD1)
IODEVICE CUNUMBR=1E00,ADDRESS=(171E,1)UNIT=3284,UNITADD=1E,PARTITION=(CSS(0),PROD1)
VTAM Gen Requirements
The VTAM gen requirements for Non-SNA controllers use an LBUILD Major Node
definition. This would be the same whether the host channel is ESCON or FICON.
An example definition for a BSC platform communicating through the FEP-4600 might
look like this:
LOCNSNA1 LBUILD
TNSD000 LOCAL CUADDR=800,
TERM=3277
MODETAB=TABNS,
DLOGMOD=NS32702,
FEATURE=EDATS
TNSD001 LOCAL CUADDR=801,
TERM=3277
MODETAB=TABNS,
DLOGMOD=NS32702,
FEATURE=EDATS
TNSD002 LOCAL CUADDR=802,
TERM=3277
MODETAB=TABNS,
DLOGMOD=NS32702,
FEATURE=EDATS
TNSD003 LOCAL CUADDR=803,
TERM=3277
MODETAB=TABNS,
DLOGMOD=NS32702,
FEATURE=EDATS
.
.
.
TNSD031 LOCAL
CUADDR=81F,
TERM=3284
MODETAB=TABNS,
DLOGMOD=NS3284,
FEATURE=MODEL2