Browse Prior Art Database

Platform Independent SQL Interface Architecture

IP.com Disclosure Number: IPCOM000107397D
Original Publication Date: 1992-Feb-01
Included in the Prior Art Database: 2005-Mar-21
Document File: 3 page(s) / 103K

Publishing Venue

IBM

Related People

Jordan, MS: AUTHOR [+5]

Abstract

This article describes the architecture needed to support a platform independent SQL interface. This architecture supports platform independence it two ways. First, the application program can run on any platform with only a recompile of the existing code. Second, the application program can access databases on any of the platforms and does not need to change if a database is migrated from one platform to another.

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

Platform Independent SQL Interface Architecture

       This article describes the architecture needed to support
a platform independent SQL interface.  This architecture supports
platform independence it two ways.  First, the application program
can run on any platform with only a recompile of the existing code.
Second, the application program can access databases on any of the
platforms and does not need to change if a database is migrated from
one platform to another.

      The architecture consists of the following key parts:
o    The Application Programming Interface (API) - this is a syntax-
consistent set of requests that the application program may call to
perform the data base tasks.  These requests may reside on any node
which can communicate with the database node via the message
transport mechanism.
o    A control program, which is resident on the database node.  This
program supports start-up and shut-down of the remaining programs in
a coordinated manner.  This program also coordinates restart/
recovery in the event of program exceptions.
o    An interface program, an agent which is resident on the data
base node.  This program provides the direct interface to the SQL
database on behalf of the application program.  A pool of available
agents is maintained to process requests.  At peak times additional
agents can be started to provide adequate concurrent database
connections.  These dynamically started programs will later stop
themselves when they are no longer needed, thus freeing up system
resources.
o    A connection control table which is resident on the data base
node.  This table provides the control mechanism for determining
which agents are busy with a current connection (a session) or are
available for work.
o    A dispatcher program which is resident on the data base node.
This program routes requests to an appropriate agent for processing.
Subsequent requests for an existing connection are forwarded directly
to the agent for that session based on information in the connection
control table.

      One or more data bases can be serviced by...