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

37x5 to FEP-4600 Migration and Planning Guide
707117-003 2-15
XID value that will be configured on those platforms. Together these two parameters
define an 8 character hex sequence. The IDBLK typically identifies the type of device
(for example a 3174 type controller always uses ‘017’ for the first 3 characters of the
XID). The IDNUM defines a unique 5 digit hex number for the remaining 5 characters.
Operations of the FEP-4600 XCA interface during the connection process involves the
PU 2.0 platform sending its XID through the FEP-4600’s XCA interface to VTAM for
processing (matching the XID to a SWNET PU definition). If a match is found the
connection is established, if not the remote platform will be disconnected. A list of nodes
that have failed to establish a connection is kept on the FEP-4600 and can be
conveniently viewed to aid in troubleshooting.
Example Token Ring XCA Definition:
TRCXCA VBUILD TYPE=XCA
PORTC66
PORT MEDIUM=RING, (Token Ring)
CUADDR=C66,
SAPADDR=4,
ADAPNO=
2 (FEP-4600 3 rd Token Ring Adapter)
GRPC66 GROUP ANSWER=ON,
CALL=IN,
AUTOGEN=(6,L,P), (Number of Concurrent PUs)
ISTATUS=ACTIVE
Example Ethernet XCA Definition:
ETHXCA VBUILD TYPE=XCA
PORTC67 PORT
MEDIUM=CSMACD, (Ethernet)
CUADDR=C67,
SAPADDR=4,
ADAPNO=
0 (FEP-4600 1 st Ethernet Adapter)
GRPC67 GROUP ANSWER=ON,
CALL=IN,
AUTOGEN=(6,L,P), (Number of Concurrent PUs)
ISTATUS=ACTIVE