The following restrictions apply to components and features when using IPv6:
- Enterprise Server listeners can only listen on either IPv4 or IPv6 addresses, not both. A listener configured to listen on all addresses (with
a requested endpoint of "*") will only listen on IPv4 addresses. To listen on an IPv6 address, a listener must be configured
to use a specific IPv6 address, or a hostname that resolves to an IPv6 address.
- CAS support for IPv6 is limited. Some features, such as CICS Web Interface and CICS Web Services, may not work with IPv6.
- The Mainframe Subsystem EZ Sockets APIs (EZASOKET and EZACICAL) do not support IPv6.
- IPv6 has not been tested with traditional CCI clients and servers such as Fileshare.
- IPv6 address zone indexes, also known as scope IDs, are ignored by
Enterprise Server. These appear in IPv6 addresses as a percent sign followed by a number or string, appended to the main part of the address,
and are used to identify a network interface when an address is not globally unique.
- There are cosmetic issues with IPv6 addresses in some contexts, such as in ESMAC.
IPv6 support for
Enterprise Server for .NET is unchanged since 5.0.