Browse Prior Art Database

OS/2 Extended Edition Database Manager Utility Process Model

IP.com Disclosure Number: IPCOM000035172D
Original Publication Date: 1989-Jun-01
Included in the Prior Art Database: 2005-Jan-28
Document File: 4 page(s) / 101K

Publishing Venue

IBM

Related People

Hernandez, R: AUTHOR [+2]

Abstract

This article describes the OS/2 Utility Process Model used to execute the OS/2 Extended Edition Database Manager Utilities as separate applications that are run along with the caller's application without the caller having to disconnect from the data base.

This text was extracted from a PDF file.
At least one non-text object (such as an image or picture) has been suppressed.
This is the abbreviated version, containing approximately 55% of the total text.

Page 1 of 4

OS/2 Extended Edition Database Manager Utility Process Model

This article describes the OS/2 Utility Process Model used to execute the OS/2 Extended Edition Database Manager Utilities as separate applications that are run along with the caller's application without the caller having to disconnect from the data base.

In the course of a normal OS/2 Data Base Manager transaction, a given process will do a "START USING DATA BASE" command to initiate a work session followed by the SQL commands to log the session of work. When that session of work is complete, either a "COMMIT" or "ROLLBACK" is executed to force or release the changes to the data base.

The OS/2 Data Base Manager allows for only one work session (i.e., Start Using Data Base) to be in effect per process. Since the OS/2 Data Base Manager Utilities are in themselves a stand-alone application, there may or may not be a session of work already started or connected to the data base when they are called in the application process.

(Image Omitted)

The OS/2 Data Base Manager Utility Process Model allows for stand alone and parallel connectivity to a data base without the user releasing data base resources that it may already have in a data base work session.

Parallel connectivity (Fig. 1) allows for the calling application (e.g., Query Manager) to call an OS/2 DBM Utility even though it is already connected to the data base. The OS/2 DBM Utility Application Program Interface will check the input parameters and, if everything checks, then it will spin off another process containing the actual Utility SQL Driver and support functions. Both the calling application and the OS/2 Data Base Manager Utility will be connected to the same data base.

Stand-alone connectivity Example 1 (Fig. 2) allows for the calling application (e.g., Query Manager) to call an OS/2 DBM Utility to perform a task on Data ...