Browse Prior Art Database

Removable ANCHOR Point for OS/2 Extended Edition Interprocess Data Areas and Control Blocks

IP.com Disclosure Number: IPCOM000036770D
Original Publication Date: 1989-Oct-01
Included in the Prior Art Database: 2005-Jan-29
Document File: 2 page(s) / 13K

Publishing Venue

IBM

Related People

Arnold, H: AUTHOR [+4]

Abstract

Disclosed is a method that allows the user to dynamically allocate resources required by the OS/2* Extended Edition Database Manager whenever the Database Manager is needed and to allow those resources to be retained as using application processes are created and terminated. It also allows the user to regain those resources for other applications whenever the Database Manager is no longer required.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 54% of the total text.

Page 1 of 2

Removable ANCHOR Point for OS/2 Extended Edition Interprocess Data Areas and Control Blocks

Disclosed is a method that allows the user to dynamically allocate resources required by the OS/2* Extended Edition Database Manager whenever the Database Manager is needed and to allow those resources to be retained as using application processes are created and terminated. It also allows the user to regain those resources for other applications whenever the Database Manager is no longer required.

This method solves at least the following problems:

Provides a persistent anchor point for resources that

are shared between processes. Without this, the shared

resources are lost whenever there are no application

processes using the Database Manager. This causes

performance and serialization problems the next time an

application uses the Database Manager.

Allows the user to release these resources if the

Database Manager is no longer required, freeing the

resources for other applications.

DESCRIPTION OF METHOD: In order to maximize performance, the Database Manager code runs in the user's application process. Since there could be several applications accessing the same database concurrently, serialization and maintenance of states must be accomplished through the use of globally shared areas and control blocks. Also to maximize performance, these shared resources must be available whenever the Database Manager functions require them. This can represent a large amount of RAM, memory selectors, and other OS/2 resources.

ESTABLISHING THE ANCHOR POINT: In order to use any Database Manager function a STARTDBM command is issued by the user. THe...