Entire Net-Work TCP/IP Option Release Information

Read this document carefully before installing and using Entire Net-Work TCP/IP Option version 6.3. It covers the following topics:

For complete information about the installation media for Entire Net-Work 6.4 and about new and changed features for Entire Net-Work 6.4, read Entire Net-Work 6.4 Release Information.


Enhancements for Entire Net-Work TCP/IP Option 6.3

The following enhancements have been made to this release of Entire Net-Work TCP/IP Option.

Support for IBM Socket Option TCP_NODELAY

Entire Net-Work 6.3 SP2 introduces support for the IBM socket option TCP_NODELAY. TCP_NODELAY indicates whether data sent over the socket is subject to the Nagle algorithm (RFC 896). For more information, refer to your IBM documentation.

Entire Net-Work 6.3 SP2 provides new TCPI and TCPX DRIVER and LINK parameters, called NODELAY, used to indicate whether the IBM socket option TCP_NODELAY is enabled or disabled for a link.

For more information about TCPI DRIVER and LINK statement parameters, read TCP/IP DRIVER Statement and TCP/IP LINK Statement. For more information about TCPX DRIVER and LINK statement parameters, read TCPX DRIVER Statement and TCPX LINK Statement.

IPv6 Support

Entire Net-Work 6.3 SP1 introduces support for IPv6 communications via the Entire Net-Work TCP/IP and Simple Connection line drivers.

  • A new ALLOWIP6 parameter has been added to both the TCPI and TCPX DRIVER statements. This parameter allows you to specify whether the line driver will accept connections using IPv6 communication. For more information about TCPI DRIVER statement parameters, read TCP/IP DRIVER Statement. For more information about TCPX DRIVER statement parameters, read TCPX DRIVER Statement.

  • A new V6IPADDR parameter has been added to both the TCPI and TCPX LINK statements. This parameter allows you to specify the IPv6 address of the remote host associated with the line driver link. For more information about TCPI LINK statement parameters, read TCP/IP LINK Statement. For more information about TCPX LINK statement parameters, read TCPX LINK Statement.

e-Business Connections to Open System Databases

Entire Net-Work 6.3 SP1 includes enhancements to the Simple Connection Line Driver (TCPX) so it now allows e-business connections between classic mainframe applications and non-mainframe databases served by Entire Net-Work 7 in open systems environments. This was previously only possible using classic TCP/IP line driver (TCPI) connections to Entire Net-Work 7.

Note:
Mainframe-to-mainframe connections are not allowed via the Simple Connection Line Driver (TCPX).

For more information, read Simple Connection Line Driver Overview.

TCPX DRIVER Connection and Disconnection Message Suppression

If you apply zap WT632005 to your Entire Net-Work TCP/IP Option 6.3 SP2 installation, you can now suppress the NETP818I and NETP819I connection and disconnection messages from your log, eliminating clutter in the log file.This is accomplished by a new TCPX DRIVER parameter provided in the zap: SUPMSGS.

For more information, read SUPMSGS Parameter.

zEnterprise Data Compression (zEDC) Support

Effective with version 6.3 SP2, zEnterprise Data Compression (zEDC) is supported on z/OS systems. This support comes in the form of two new LINK parameters for the TCPI line driver: ZEDC and ZEDCLOG. The ZEDC parameter indicates whether zEDC compression can occur for the link; the ZEDCLOG parameter identifies the level of trace data that should be logged for zEDC compression processing. For more information, read TCP/IP LINK Statement.

New and Changed TCP/IP Line Driver (TCPI) DRIVER and LINK Parameters

The following table summarizes the new TCP/IP Line Driver (TCPI) DRIVER and LINK parameters introduced in Entire Net-Work 6.3:

Parameter DRIVER or LINK Statement? New or Changed? Description Introduced in Release
ALLOWIP6 DRIVER New This new parameter can be used to indicate whether the TCPI line driver will accept connections using IPv6 communication. 6.3 SP1
API DRIVER Changed A new value option EZA has been added for the TCPI DRIVER parameter API. This parameter value loads the z/VSE interface NWTCPEZA. This value can be used only with the TCP/IP stack from Barnard Software, Inc. 6.3 SP1
NODELAY Both New This new parameter can be used to indicate whether the IBM socket option TCP_NODELAY is enabled or disabled for a link. 6.3 SP2
V61IPADDR LINK New This new parameter can be used to specify the IPv6 address of the remote host associated with the TCPI link. 6.3 SP1
ZEDC LINK New This new parameter indicates whether zEnterprise Data Compression (zEDC) compression can occur for the link. 6.3 SP2
ZEDCLOG LINK New This new parameter indicates what level of trace data will be logged for zEDC compression processing. 6.3 SP2

For more information about TCPI DRIVER statement parameters, read TCP/IP DRIVER Statement. For more information about TCPI LINK statement parameters, read TCP/IP LINK Statement.

New and Changed Simple Connection Line Driver (TCPX) DRIVER and LINK Parameters

The following table summarizes the new Simple Connection Line Driver (TCPX) DRIVER and LINK parameters introduced in Entire Net-Work 6.3:

Parameter DRIVER or LINK Statement? New or Changed? Description Introduced in Release
ACQUIRE LINK New This parameter is already in use for the TCPI line driver. It was added to the TCPX line driver in this release. It can be used to specify whether or not a connection with the remote node should be attempted when the driver is opened for the first time (during system initialization). 6.3 SP1
ALLOWIP6 DRIVER New This new parameter can be used to indicate whether the TCPX line driver will accept connections using IPv6 communication. 6.3 SP1
API DRIVER Changed A new value option EZA has been added for the TCPX DRIVER parameter API. This parameter value loads the z/VSE interface NWTCPEZA. This value can be used only with the TCP/IP stack from Barnard Software, Inc. 6.3 SP1
RESTART LINK New This parameter is already in use for the TCPI line driver. It was added to the TCPX line driver in this release. It can be used to specify the retry interval in seconds and the number of retries that are made to start the connection to the remote node. 6.3 SP1
NODELAY Both New This new parameter can be used to indicate whether the IBM socket option TCP_NODELAY is enabled or disabled for a link. 6.3 SP2
SUPMSGS DRIVER New This new parameter allows you to suppress the NETP818I and NETP819I connection and disconnection messages from your log, eliminating clutter in the log file. 6.3 SP2 (via zap WT632005)
V61IPADDR LINK New This new parameter can be used to specify the IPv6 address of the remote host associated with the TCPX link. 6.3 SP1
WEIGHT LINK New This parameter is already in use for the TCPI line driver. It was added to the TCPX line driver in this release. It can be used to specify the weight of this link with respect to other links going to the same node. 6.3 SP1

For more information about TCPX DRIVER statement parameters, read TCPX DRIVER Statement. For more information about TCPX LINK statement parameters, read TCPX LINK Statement.

New Simple Connection Line Driver (TCPX) LINK Command

With Entire Net-Work 6.3 SP1, the CONNECT operator command has been added to the Simple Connection Line Driver (TCPX) LINK commands. This command mirrors the CONNECT LINK operator command used by the TCP/IP line driver.

For more information, read Simple Connection Line Driver Operator Commands.

Requirements and Restrictions

Compatibility with Earlier Versions of the Line Drivers

The TCP/IP line driver supports connections with TCP/IP line drivers from all prior versions of Entire Net-Work.

The Simple Connection Line Driver supports the same connections that were supported in all prior versions of Entire Net-Work.

TCP/IP Transport Providers Supported

Entire Net-Work 6.3 supports the following levels of TCP/IP transport providers:

Platform TCP/IP Protocol Supported
z/OS

IBM TCP/IP for z/OS Version 1.10, 1.11, and 1.12.

z/VSE

IBM and Connectivity Systems TCP/IP z/VSE Version 4.2 and 4.3.

BS2000/OSD Sockets Subsystem

Sockets Version 2.0 and above.

For Sockets 2.2 and above, the SOC6 subsystem will be used, otherwise the SOCKETS subsystem is used.

When accessing via IPV6 addressing, a SOC6 subsystem with Sockets 2.5 is the minimum requirement.