Browse Prior Art Database

Enabling TCP/IP Communication in OV/MVS

IP.com Disclosure Number: IPCOM000119852D
Original Publication Date: 1991-Mar-01
Included in the Prior Art Database: 2005-Apr-02
Document File: 1 page(s) / 39K

Publishing Venue

IBM

Related People

Janis, FL: AUTHOR [+2]

Abstract

This article describes how to support TCP/IP communication in OfficeVision*/MVS (OV/MVS). OV/MVS Version 2 is based on a conversational communication protocol. This protocol (LU 6.2), works by having the receiver of the conversation invoked as a transaction program when the conversation is begun. TCP/IP is a messaging-based protocol which assumes the receiver of the message is active, ready to receive. The design for OV/MVS Version 2 is the Client/Server Model. It is necessary that the service program in OV/MVS should not have to be aware which protocol is being used to convene a request from a client.

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

Enabling TCP/IP Communication in OV/MVS

      This article describes how to support TCP/IP
communication in OfficeVision*/MVS (OV/MVS). OV/MVS Version 2 is
based on a conversational communication protocol. This protocol (LU
6.2), works by having the receiver of the conversation invoked as a
transaction program when the conversation is begun.  TCP/IP is a
messaging-based protocol which assumes the receiver of the message is
active, ready to receive. The design for OV/MVS Version 2 is the
Client/Server Model. It is necessary that the service program in
OV/MVS should not have to be aware which protocol is being used to
convene a request from a client.

      The solution is to provide an active listener for requests to
OV/MVS from TCP/IP protocol clients.  The Environment Facility
(EF/MVS) can provide such a function. When EF/MVS is initialized, it
starts up a subtask whose function is to listen for TCP/IP requests.
When a request for a connection is received, the EF subtask begins an
LU 6.2 conversation with an APPC Office Server.  The receiver of the
LU 6.2 conversation is the Request Handler Transaction Program (RHTP)
of the Application Request Handler (ARH). The information passed to
ARH is the socket descriptor where the connection request is waiting.
The ARH performs the accept function and passes the request to the
Office Server.  When the Office Server is done, the data is passed
back to the TCP/IP client by ARH using the send function.  Then the
LU 6.2 co...