This section describes the TCP/IP transport providers supported:
Under z/OS, IBM's eNetwork Communications Server is supported.
Under z/VSE, Connectivity Systems TCP/IP stack and API or IBM TCP/IP for z/VSE (software provided by Connectivity Systems) only are supported.
Under BS2000/OSD, Sockets, a component of Open Net Server, is supported.
This document covers the following topics:
In z/OS environments, OpenEdition sockets (API=OES) or the high performance native sockets interface (API=HPS) are used to communicate with the IBM TCP/IP address space. A valid OpenEdition security context, referred to as an OMVS segment, must be defined for Entire Net-Work. For more information, see the IBM document z/OS OpenEdition Planning Guide.
If the OMVS segment is not properly defined, TCP/IP driver initialization will fail with error 156. The Entire Net-Work error message received is NETP600I if API=HPS or NETP700I if API=OES.
In z/VSE environments, the native Sockets interface is used to communicate with the TCP/IP partition. To use the Connectivity Systems TCP/IP stack and API, users must ensure that the Adabas program ADARUN, which is used to invoke Entire Net-Work, has been linked with ADMODE (31). This is the distributed default upon release for both the Adabas library and the Adabas limited library.
In BS2000/OSD environments, the Sockets subsystem is used to communicate with BCAM:
BS2000/OSD Versions 5 and above are supported.
Sockets subsystem versions 2.0 and above are supported. This version
number can be determined using the SHOW-SUBSYSTEM-STATUS
SUBSYSTEM-NAME=SOCKETS command.