Browse Prior Art Database

Locate the Os/2 Extended Edition Database Manager's Database Information

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

Publishing Venue

IBM

Related People

Atkinson, RL: AUTHOR [+3]

Abstract

This article describes the method that the OS/2* Extended Edition Database Manager uses to locate a vital control block from any process at any given point after database connection has begun.

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

Page 1 of 1

Locate the Os/2 Extended Edition Database Manager's Database Information

This article describes the method that the OS/2* Extended Edition Database Manager uses to locate a vital control block from any process at any given point after database connection has begun.

The control block, referred to as the Database Control Block (SQLEDBCB), must be locatable from processes which are created during or after connection to a database. This Database Control Block contains vital information concerning the location of the database, configurable database parameters, data areas needed by code which services database requests and more. When needed processes, like the Log Process, are created they have no knowledge of where the Database Control Block is. By calling a Basic Support Utilities (BSU) function and providing the database path specification, the corresponding Database Control Block can be located. An anchor point for a chain of Database Control Blocks is maintained in an area that is global to all processes - SQLEKRCB. The location of this chain is known to BSU but not to application users, etc. This chain is searched until the appropriate control block is located and then the corresponding address is returned.

Without this function, Database Manager would have great difficulty in freely creating other processes as needed. * Trademark of IBM Corporation.

1