Browse Prior Art Database

Transmission Control Protocol/Internet Protocol Connection for Virtual Storage Extended/Enterprise Systems Architecture via Service-Call Logical Processor or via Local Area Network Resource Extension and Services

IP.com Disclosure Number: IPCOM000118707D
Original Publication Date: 1997-May-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 4 page(s) / 127K

Publishing Venue

IBM

Related People

Ngo-Anh, T: AUTHOR

Abstract

Currently, there is a lack of native Transmission Control Protocol/Internet Protocol (TCP/IP) Solutions on Virtual Storage Extended (VSE). To date, Virtual Storage Extended/Enterprise Systems Architecture (VSE/ESA) does not provide a TCP/IP support in its base operating system. In order to access to TCP/IP, the user must install a vendor software product and needs to have a RISC/6000 use the services (e.g., Telnet, FTP) based on the TCP/IP and to connect to the Internet.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 49% of the total text.

Transmission Control Protocol/Internet Protocol Connection for Virtual
Storage Extended/Enterprise Systems Architecture via Service-Call
Logical Processor or via Local Area Network Resource Extension and
Services

      Currently, there is a lack of native Transmission Control
Protocol/Internet Protocol (TCP/IP) Solutions on Virtual Storage
Extended (VSE).  To date, Virtual Storage Extended/Enterprise Systems
Architecture (VSE/ESA) does not provide a TCP/IP support in its base
operating system.  In order to access to TCP/IP, the user must
install a vendor software product and needs to have a RISC/6000 use
the services (e.g., Telnet, FTP) based on the TCP/IP and to connect
to the Internet.

      Due to its system restrictions (e.g., system tasking model,
non-POSIX conformity), it is not possible to port TCP/IP from other
OS platforms (even within the S/390).

There are two solutions to solve this problem:
  1.  TCP/IP Connection for VSE/ESA via Service-Call Logical
       Processor (SCLP)
      This solution will solve the described problems by using
       the hardware capability of the ES9000* products and S/390*
       Parallel Enterprise Server of the Complementary Metal Oxide
       Semiconductor (CMOS) product family on the SCLP and their
       software related component: the service processor calls to
       communicate with the system hardware console, which has its
       own OS, to establish a TCP/IP connection to the outer world.
  2.  TCP/IP Connection for VSE/ESA via Local Area Network
       Resource Extension and Services (LANRES)
      This solution will solve the described problem by using
       LANRES as transport and interface layer to establish a
       TCP/IP connection to the network.

      The solution can be handled by using SCLP.  The System hardware
console of the ES9000 and the S/390 Parallel Enterprise Servers is
running under OS/2 and is able to share a predefined portion of
system memory to perform the communication between the main processor
and the  service processor (the SCLP).  IBM* also defines a set of
service calls to let the operating system communicate with the
hardware. This  capability could now be used to pass the data and
instruct the OS on the system console from VSE/ESA to set up a TCP/IP
connection to the network.  The system hardware console only needs to
have a LAN token ring card and TCP/IP for OS/2 to be installed.

      With this solution, the main operating system (VSE/ESA, in this
case) does not have to have the TCP/IP support but can store and send
the TCP/IP data to the TCP/IP network through its system hardware
console which equipped with the TCP/IP software code and the LAN
token ring adapter (Fig. 1).

      From a VSE partition, the user could call a program which
intercepts the TCP/IP commands and the data, passes them to the
predefined system memory by a series of system service p...