This document lists the Entire Net-Work 6.3 enhancements.
While a license was issued in past releases of Entire Net-Work, only warning messages were issued if license problems were encountered. With Entire Net-Work 6.3 SP2, these licenses are enforced and Entire Net-Work will terminate if:
No license key is available or provided to Entire Net-Work;
The license key provided has been manipulated;
The product name in the license key does not match the product for which the license is being used; or
The operating system in the license key does not match the operating system on which the license is being used, although changes in operating system version are not checked.
For complete information on licensing your Entire Net-Work software, read Software AG Mainframe Product Licensing and your Entire Net-Work installation procedure.
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.
Note:
The setting of this parameter is only effective if the API parameter
is also set to "OES" or
"HPS."
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.
Entire Net-Work 6.3 SP2 introduces support that allows you to display all posted command queue elements (CQEs) using a new DISPLAY CQ command. DISPLAY CQ displays information about each CQE, including command code, database and file number, buffer length, sequence number, age, job name, user ID, and status.
For more information, read DISPLAY CQ Example.
Entire Net-Work 6.3 SP2 introduces support that allows you to display detailed information about a specific command queue element (CQE) using a new DISPLAY CQE command. It takes the command sequence number as input, which can be determined from the output of a DISPLAY CQ command.
For more information, read DISPLAY CQE Example.
Entire Net-Work 6.3 SP2 introduces support that allows you to display details about local targets. This support is provided using a new DISPLAY DETAIL command. It allows you to display details about the node , its location, name and local targets. The local target information contains the target ID, target type, job name and the job number/ID that started it as well as product details. For more information, read DISPLAY DETAIL Examples.
Entire Net-Work 6.3 SP2 introduces support that allows you to display all user buffers (UBs) for commands in wait status. This support is provided using a new DISPLAY UBQ command. It displays information about each UB in process, including the command code, database and file number, checksum number, UB flags and address, age, job name and user ID. For more information, read DISPLAY UBQ Example.
Effective with version 6.3 SP2, zEnterprise Data Compression (zEDC) is supported on z/OS systems. At a minimum, this support requires that you have a z/OS V2R1 operating system, an IBM zEnterprise zEC12 GA2 server, and a zEDC Express coprocessor. For complete information on z/OS requirements for zEDC support, refer to IBM documentation regarding zEnterprise Data Compression (zEDC).
Entire Net-Work support for zEDC comes in the form of two new NODE statement parameters as well as two new LINK parameters for the CTCA, FCTC, TCPI, VTAM and XCF line drivers.
Two new NODE statement parameters have been introduced: ZEDCINIT and ZEDCSZ. The ZEDCINIT parameter indicates whether zEDC compression can occur for the node; the ZEDCSZ parameter specifies, in kilobytes, the smallest payload that may be compressed by zEDC compression. For more information, read Entire Net-Work NODE Statement.
The ZEDC and ZEDCLOG are new LINK parameters valid for use with the CTCA, FCTC, TCPI, VTAM, and XCF line drivers. 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 about the LINK statement for the corresponding line driver.
Additional statistics are produced by the DISPLAY STATS command and at shutdown when messages have been compressed with zEDC. For more information, read DISPLAY STATS Example.
Error messages specific to Entire Net-Work's zEDC support begin with the message prefix "NETE". These messages are described in NETE* - zEnterprise Data Compression (zEDC) Support Messages.
In Entire Net-Work 6.3 SP2, the counters for the following line drivers have been expanded to eight bytes to prevent the various driver and link statistics from overflowing:
CTCA - Channel-to-channel line driver
FCTC -- Fast channel-to-channel line driver
TCPI -- TCP/IP line driver
TCPX -- Simple Connection line driver
XCF -- XCF (Cross-system coupling) line driver
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.
XCF line driver 6.3 SP1 and SP2 provide a new EXHS parameter for both the XCF line driver DRIVER and LINK statements. This new parameter indicates whether extended handshakes should be used. Specify this parameter only as advised by Software AG; it was created to provide compatibility between the Entire Net-Work XCF Option 6.3 releases and the 6.1 SP2 and 6.2 SP2 releases. Support for this new parameter is provided with the following zaps applied:
WF631004 and WM631025 for version 6.3 SP1;
WF632003, WM632009, and WM632013 for version 6.3 SP2.
For more information, read XCF DRIVER Statement and XCF LINK Statement.
XCF line driver 6.3 SP2 provides a new RCVBFNUM parameter for the XCF line driver DRIVER statement. This new, optional, parameter allows you to specify the number of entries in the receive buffer table. The minimum value you can specify is 100, the maximum is 99999. The default is 4096.
Note:
In almost all cases the default table size is adequate. We recommend
that you do not alter the RCVBFNUM parameter setting unless directed to do so
by Software AG.
For more information, read XCF DRIVER Statement.
The 6.3 FCTC line driver is incompatible with previous releases of FCTC. To address this in version 6.3 SP1, an Entire Net-Work CTC Option L001 library was made available to you that enabled compatible FCTC connections between 6.3 and 6.2 SP2 nodes. This L001 library provided code that allowed a 6.3 node to detect a connection to a prior version of FCTC and automatically convert that connection to a compatible 6.2 SP2 connection.
This FCTC compatibility processing has been automatically included in Entire Net-Work CTC Option 6.3 SP2. You no longer need the L001 library. Activation of compatibility mode is controlled using a new FCTC DRIVER parameter called COMPAT. For complete information about the COMPAT parameter, read FCTC Line Driver Compatibility and CTCA and FCTC DRIVER Statements.
A description of the enhancements made to the FCTC line driver in version 6.3 is provided in FCTC Line Driver Enhancements.
The following changes were made to the FCTC line driver in version 6.3 SP1:
Note:
The 6.3 FCTC line driver is incompatible with previous releases of FCTC. A
description of the methods by which this incompatibility has been addressed by
Software AG is provided in FCTC line driver
Compatibility.
Changes have been made to the FCTC line driver to support defining both the read unit and write unit in the same link.
Support for the UNIT, CHREAD, and TOKEN LINK parameters have been dropped.
New LINK parameters UNITREAD and UNITWRT have been added and are required for FCTC links. UNITREAD identifies the address of the unit that should be used for reading data; UNITWRT specifies the address of the unit that should be used for sending data.
These enhancements also allow a link to function in impaired mode; if one unit is unavailable, the other unit can function as both the read and write unit, similar to a CTCA link. Note, however, that both UNITREAD and UNITWRT must be specified.
For complete information about FCTC LINKs, read CTCA and FCTC LINK Statements.
For the FCTC DRIVER, the channel programs have been enhanced so that each read and write in a command chain is preceded by a prepare command. This further reduces the overhead of attention interrupts.
For complete information about FCTC DRIVER statements, read CTCA and FCTC DRIVER Statements.
The FCTC LINK has been enhanced to allow a link to function even if only one unit is active; this is referred to as operating in impaired mode. In this case, the active unit reverts to bidirectional communication similar to a CTCA link. For complete information about running in impaired mode, read FCTC LINKS Operating in Impaired Mode.
The DISPLAY LINKS and FCTC STATUS operator commands have also been updated also to show the status of each unit. For more information (including the syntax of the commands), read DISPLAY Command and CTCA and FCTC Operator Commands.
In prior releases, problems could occur when setting up the Adabas Review hub across nodes using Entire Net-Work (mainframe). Entire Net-Work 6.3 SP2 now fully supports communication with the Adabas Review hub.
Note:
Entire Net-Work parameter changes may be necessary to handle the
increased traffic produced by the hub.
Entire Net-Work 6.3 SP1 supports reusable address space IDs (ASIDs) in z/OS environments. So you can now specify the z/OS REUSASID system parameter on the start command for Entire Net-Work. For example:
/S NETWORK,REUSASID=YES
For more information about the REUSASID system parameter, refer to your z/OS documentation.
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.
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.
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.
Entire Net-Work XCF Option 6.2 SP1 statistics that are triggered by the PSTATS or STATINT parameters or by the STATS operator command are now written only to DDPRINT. Other messages are written to both the console and DDPRINT. For more information, read about the XCF line driver in the Entire Net-Work XCF Option Administration Guide.
With Entire Net-Work 6.3 SP1, the DISPLAY TARGETS command now lists targets in ascending order, rather than in the unordered manner it listed them in previous releases. For an example, read DISPLAY TARGETS Example.
With Entire Net-Work 6.3 SP1, the DISPLAY ZAPS command now lists the full zap name in its output, not only the zap number. Its output now more closely resembles the zap output for Adabas. For an example, read DISPLAY ZAPS Example.
Entire Net-Work 6.3 SP1 increases the limitation on messages that can be handled by Entire Net-Work. In prior releases, the message size limitation was approximately 16 megabytes. As of this release (and in later releases), the maximum size of a message that can be handled by Entire Net-Work has increased to approximately two gigabytes (2G), limited by parameter settings and storage availability.
Entire Net-Work 6.3 SP1 introduces a new setting for the LOG parameter: LIMITED. The LIMITED setting (LOG=LIMITED) performs the same function as LOG=FULL, except that most log entries are limited to 256 bytes of data. In many cases, this makes the amount of data logged more manageable.
You can also specify the new LIMITED value in the SET LOG command.
For more information, read LOG Parameter and SET LOG Command.
Entire Net-Work 6.3 SP1 introduces several zap table changes.
The format of zap table elements has been altered to more closely resemble the zap table used for Adabas. In addition the full zap name is now listed, not only the zap number.
Optional zap table elements have the following format:
NETZOPT Date yyyy-mm-dd, Version: vv.rr, SP ss, Base base-id
Zaps zapid zapid2
All other zap table elements have the following format:
NETWRK Date yyyy-mm-dd, Version: vv.rr, SP ss, Base base-id
Zaps zapid1 zapid2
The zap table is now displayed after the line drivers have been initialized, but before license verification.
The following table summarizes new and changed parameters introduced in Entire Net-Work 6.3 for its line drivers.
| Parameter | Line Driver | DRIVER or LINK Statement? | New or Changed? | Description | Introduced in Release |
|---|---|---|---|---|---|
| ACQUIRE | TCPX | 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 | TCPI | DRIVER | New | This new parameter can be used to indicate whether the line driver will accept connections using IPv6 communication. | 6.3 SP1 |
| API | TCPI | DRIVER | Changed | A new value option EZA has been added for the 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 |
| EXHS | XCF | Both | New | This new parameter indicates whether extended handshakes should be used. Specify this parameter only as advised by Software AG; it was created to provide compatibility between the Entire Net-Work XCF Option 6.3 releases and the 6.1 SP2 and 6.2 SP2 releases. Zaps are required to support this functionality. For more information, read XCF DRIVER and LINK Backward Compatibility. | 6.3 SP1 |
| NODELAY | TCPI | 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 |
| RCVBFNUM | XCF | DRIVER | New | This new, optional, parameter allows you to specify the number of entries in the receive buffer table. The minimum value you can specify is 100, the maximum is 99999. The default is 4096. | 6.3 SP2 |
| RESTART | TCPX | 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 |
| SUPMSGS | TCPX | 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 | TCPI | LINK | New | This new parameter can be used to specify the IPv6 address of the remote host associated with the link. | 6.3 SP1 |
| WEIGHT | TCPX | 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 |
| ZEDC | TCPI | LINK | New | This new parameter indicates whether zEnterprise Data Compression (zEDC) compression can occur for the link. | 6.3 SP2 |
| ZEDCLOG | TCPI | LINK | New | This new parameter indicates what level of trace data will be logged for zEDC compression processing. | 6.3 SP2 |
The following table summarizes the new and changed operator commands introduced in Entire Net-Work 6.3:
| Command | New or Changed? | Description | Introduced in Release |
|---|---|---|---|
| DISPLAY CQ | New | This command displays information about each command queue element (CQE), including command code, database and file number, buffer length, sequence number, age, job name, user ID, and status. | 6.3 SP2 |
| DISPLAY CQE | New | This command displays detailed information about a specific command queue element. | 6.3 SP2 |
| DISPLAY DETAIL | New | This command displays detailed information about local targets. | 6.3 SP2 |
| DISPLAY TARGETS | Changed | This command now lists targets in ascending order, rather than in the unordered manner it listed them in previous releases. | 6.3 SP1 |
| DISPLAY UBQ | New | This command displays all user buffers (UBs) for commands in wait status. It displays information about each UB in process, including the command code, database and file number, checksum number, UB flags and address, age, job name and user ID. | 6.3 SP2 |
| DISPLAY ZAPS | Changed | This command now lists the full zap name in its output, not only the zap number. Its output now more closely resembles the zap output for Adabas. | 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.