Interfaces supported by OMPROUTE

Table 1, Table 2, and Table 3 show the types of interfaces supported by OMPROUTE.

Table 1. Types of IPv4 interfaces (using DEVICE and LINK statements) supported by OMPROUTE
Interface type Link type Connectivity Multi-access broadcast Non- broadcast multiaccess (NBMA) Point-to-point Point-to- multi-point Futile neighbor state loop detection support
ATM ATM ATM network through OSA-2 or OSA-Express in ATM native mode No Yes No No No
CDLC CDLC 3745/3746 network through NCP No No Yes No No
CLAW IP pSeries or OEM No No Yes Yes and no (See Note 2) No
CTC CTC z/OS® through channel-channel adapter No No Yes No No
HCH HCH Another host through a hyperchannel adapter No Yes No No No
LCS IBMTR, ETHERNET, 802.3 LAN through OSA in LCS mode (including ATM LAN emulation), 3172, 2216, Token Ring, Ethernet, Ethernet 802.3, FDDI Yes No No No Yes
MPCIPA IPAQENET, IPAQTR LAN through OSA-Express in QDIO mode (Gigabit Ethernet, Fast Ethernet, ATM Ethernet LANE, High Speed Token Ring) Yes No No No Yes
MPCIPA: IPAQIDIO (for internal QDIO) IPAQIDIO (for internal QDIO) Another TCP/IP within same CPC Yes No No No Yes
MPCOSA OSAENET, OSAFDD Fast Ethernet, FDDI No Yes No No No
MPCPTP MPCPTP z/OS, pSeries, Cisco CIP, CS/NT, or OEM z/OS, No No Yes Yes No
MPCPTP MPCPTP (for XCF) Another TCP/IP within same z/OS sysplex No No Yes Yes No
MPCPTP (for IUTSAMEH) MPCPTP (for IUTSAMEH) Another TCP/IP within same z/OS sysplex No No Yes Yes No
SNAIUCV SAMEHOST SNA network through a SNALINK LU 0 application on same z/OS No No Yes No No
SNALU62 SAMEHOST SNA network through SNALINK LU6.2 application on same z/OS No No Yes No No
X25NPSI SAMEHOST X.25 network through X.25 appl on same z/OS No Yes Yes (See Note 3) No No
Notes:
  1. For more information about the DEVICE and LINK statements for the interfaces, see Figure 1.
  2. Becomes point-to-multipoint capable when the P2MP parameter option is specified on the LINK statement.
  3. In general, SAMEHOST link type is treated as point-to-point. X.25 NPSI established as a SAMEHOST connection is also treated as NBMA because it is a switched virtual circuit (SVC) that appears to VTAM® as a switched link. In a X.25 network, SVCs provide multi-access support but they are not broadcast capable.
  4. For more information about IPv4 interfaces using the INTERFACE statement, see Table 2
Table 2. Types of IPv4 interfaces (using INTERFACE statement) supported by OMPROUTE
Interface type Connectivity Multi-access broadcast Non- broadcast multiaccess (NBMA) Point-to-point Point-to- multi-point Futile neighbor state loop detection support
IPAQENET LAN through OSA-Express in QDIO mode (Gigabit Ethernet, Fast Ethernet, ATM Ethernet LANE) Yes No No No Yes
Note: For more information about the alternative INTERFACE statements for the interfaces, see Summary of INTERFACE statements.
Table 3. Types of IPv6 interfaces supported by OMPROUTE
Interface type Connectivity Multi-access broadcast Non- broadcast multiaccess (NBMA) Point-to- point Point-to- multi-point Futile neighbor state loop detection support
IPAQENET6 LAN through OSA-Express in QDIO mode (Gigabit Ethernet, Fast Ethernet, ATM Ethernet LANE) Yes No No No Yes
IPAQIDIO6 (for internal QDIO) Another TCP/IP within the same CEC Yes No No No Yes
MPCPTP6 z/OS, pSeries, Cisco CIP, CS/NT, or OEM No No Yes Yes No
MPCPTP6 (for IUTSAMEH) Another TCP/IP within same z/OS sysplex No No Yes Yes No
MPCPTP6 (for XCF) Another TCP/IP within same z/OS sysplex No No Yes Yes No
Note: For more information about the INTERFACE statements for the interfaces, see Summary of INTERFACE statements.
Parent topic: OMPROUTE