Browse Prior Art Database

OS/2 to OS/400 Communication Transport Mechanism

IP.com Disclosure Number: IPCOM000111551D
Original Publication Date: 1994-Mar-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 80K

Publishing Venue

IBM

Related People

Thio, HC: AUTHOR

Abstract

Disclosed is a communication transport mechanism between applications on an OS/2* PWS and applications on an AS/400* system. It combines the following concepts:

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

OS/2 to OS/400 Communication Transport Mechanism

      Disclosed is a communication transport mechanism between
applications on an OS/2* PWS and applications on an AS/400* system.
It combines the following concepts:

o   It provides data transport services between an OS/2 PWS and an
    AS/400 system.

          It uses PC Support/400's data queue APIs as its underlying
    data transport mechanism.  The data queue is used to queue
    messages that are sent to it by the OS/2 application or OS/400*
    applications.  These messages are in turn read by the OS/400
    applications or OS/2 application, respectively, for processing.

o   It is capable of managing one or more communication sessions
    concurrently.

          Each communication session is made up of a pair of
    half-duplex PC Support/400 data queues, one for communication
    from OS/2 to OS/400 and the other for communication from OS/400
    to OS/2.  Each communication session is capable of servicing a
    request sent from the OS/2 application.  Corresponding to each
    communication session is an instance of the host application
    which is responsible for processing the request.  Thus, this
    invention provides the capability of servicing multiple user
    requests concurrently.  More importantly, this invention
    coordinates which request uses which communication sessions.  The
    calling application needs not worry about the communication
    setup.

o   It provides a communication-independent high-level Application
    Programming Interface (API).

          These APIs dictate the protocol used between the client (or
    OS/2 side) and the server (or OS/400 side).  It is made up of
    four APIs on the client, namely Request_New, Request_More,
    Request_Stop and Shut_Down.

    -   Request_New is used to initiate a new request.  Each request
        is made up of a header portion and a data portion.  The data
        portion can contain query information, update information or
        any other types of information which make sense between the
        client application (on OS/2) and the server application (on
        OS/400).

    -   Request_More is used to send a request that is part of the
        previous request.  This API allows the clie...