Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

Scheme for Integrating Transmission Control Protocol/Internet Protocol Socket Support in a Database Manager

IP.com Disclosure Number: IPCOM000104368D
Original Publication Date: 1993-Apr-01
Included in the Prior Art Database: 2005-Mar-19
Document File: 4 page(s) / 156K

Publishing Venue

IBM

Related People

Chang, DY: AUTHOR [+4]

Abstract

This invention provides a basic scheme that can be used to greatly ease the integration of Transmission Control Protocol/Internet Protocol (TCP/IP) socket support in the OS/2* Database Manager (DBM). In particu lar, this scheme provides an application transparent means for dealing with the problem of handling database connections from TCP/IP clients in a very independent manner from a software design point of view. Because of this design independence, this scheme allows the easy integration of the socket database connection support in prior DBM releases. Further more, this scheme allows the implementation of stand-alone socket-based DBM clients. That is, an application client support library that re quires no other DBM code in the client node.

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

Scheme for Integrating Transmission Control Protocol/Internet Protocol Socket Support in a Database Manager

      This invention provides a basic scheme that can be used to
greatly ease the integration of Transmission Control
Protocol/Internet Protocol (TCP/IP) socket support in the OS/2*
Database Manager (DBM).  In particu lar, this scheme provides an
application transparent means for dealing with the problem of
handling database connections from TCP/IP clients in a very
independent manner from a software design point of view.  Because of
this design independence, this scheme allows the easy integration of
the socket database connection support in prior DBM releases.
Further more, this scheme allows the implementation of stand-alone
socket-based DBM clients.  That is, an application client support
library that re quires no other DBM code in the client node.  While
all options for methods of adding TCP/IP support to DBM are open for
future releases, it is a much more restrictive problem to create a
method that can be retrofitted to earlier versions of DBM, thus
providing TCP/IP connection support to those clients as well.  The
problem of adding TCP/IP socket support to DBM in an easily
retrofitted manner is further aggravated by the differences between
the DBM clients in different releases.

      The figure illustrates the general architecture for the
integration of TCP/IP socket support in DBM.  Each element of the
figure is explained next.  Elements highlighted with "*" represent
new software that is necessary to implement that element.

      APP: This is the application program that contain DBM
Application Programming Interface (API) calls and/or embedded SQL
Statements.

      API: This is the existing library containing the entry points
for the APIs called by the application (APP), including the SQL
router for SQL statements.  A small code change is made to each API
function that is to become sensitive to Socket-Based DBM Servers, as
per the algorithm described later.

      API2: This is a new library containing the new dynamic SQL and
database Connection APIs that can be used by a stand-alone client.
All of the functions in the API2 library share a global API2 Control
Block data structure among themselves and among the API library
functions that operate on database connections.

      ASL1: This library contains the functions that hide the new
process model IPC scheme from the API.  For prior DBM releases this
library doesn't exist.

      ASL2: This is a new library that contains the client functions
that hide the socket based data flow from the API library.  It also
contains the client code to lookup a database entry in the database
system catalog.  All of the functions in the ASL2 library share a
global ASL2 Control Block data structure.

      ASL3: This is a new library that contain the Server Engine DBM
functions that support the API at the server.  It also contain the
functions to s...