Browse Prior Art Database

Dynamic Selection of Output Data

IP.com Disclosure Number: IPCOM000099278D
Original Publication Date: 1990-Jan-01
Included in the Prior Art Database: 2005-Mar-14
Document File: 2 page(s) / 95K

Publishing Venue

IBM

Related People

Elliott, LC: AUTHOR [+3]

Abstract

This article describes a flexible, efficient algorithm which follows static architected flows also uses information which is available only at time (i.e., the selection algorithm is based on and dynamic information).

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

Dynamic Selection of Output Data

       This article describes a flexible, efficient algorithm
which follows static architected flows also uses information which is
available only at time (i.e., the selection algorithm is based on and
dynamic information).

      After a database kernel request has been processed, data will
be returned to the application.  If the is remotely connected to the
database, this data should be built into data structures to be to the
requestor machine.  This article the techniques Remote Data Services
has designed manage the construction of output data structures.  It
shows how this design can be used for other

      Remote Data Services is a component of the OS/2* Edition Data
Base Manager.  Remote Data Services is for directing a database
kernel request to a which resides on a different machine.  The
request and any associated data must be transmitted to the database.
In addition, the return data and error must be transmitted to the
"requestor" after the has been processed.  To direct the request,
complex structures must be built and sent between the partner

      The main components of the design are:
   1.   the return data definition table which defines
        what output data structures may be returned from
        particular database kernel requests,
   2.   the return data table which contains the
        instructions for building the output data
        structures, and
   3.   the return data indicator table which allows the
        return data definition to be updated dynamically.

      Return Data Definition Table: table contains an entry for every
database kernel  Each entry contains a description of the output
structures for that request.  It is possible that some the output
data structures may vary depending on the to the database kernel
request.  To handle this, the data definition table makes use of
pre-processing  They serve the same purpose as on the requestor for
building the data structures for a kernel i.e., the pre-processing
functions will determine it is necess...