Browse Prior Art Database

Status Correlation Application Programming Interface

IP.com Disclosure Number: IPCOM000122286D
Original Publication Date: 1991-Nov-01
Included in the Prior Art Database: 2005-Apr-04
Document File: 3 page(s) / 94K

Publishing Venue

IBM

Related People

Johnson, WJ: AUTHOR [+2]

Abstract

A program interface is described which solves the problem of managing pending status when changing connections to a new logical unit (LU) pair, redefined routing paths with or without new distribution management processes or migrating to a new level of server software.

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

Status Correlation Application Programming Interface

      A program interface is described which solves the problem
of managing pending status when changing connections to a new logical
unit (LU) pair, redefined routing paths with or without new
distribution management processes or migrating to a new level of
server software.

      This article describes an Application Programming Interface
(API) for use by all distribution processes running on a specific
machine.  The API isolates delivery id management from the server(s)
so that migrated server levels or redefined routing paths will not
affect the pending status entries needed by forthcoming partner LU
communications.  Furthermore, an API architecturally enforces an
optimal method for maintaining status. Function interfaces for
delivery status management, universal status correlation API and
isolation of status management from processes on a particular machine
to facilitate migration and redefined routing paths are all
facilitated features.

      The following is a sample implementation of the API. SQL is
used to describe the required database table, index and associated
I/O functionality. Code which drives the SQL is intuitive.
  EXEC SQL CREATE TABLE OV2LAN.STATUS_CORRELATE
      (ENTRY_USER                CHAR(N1) NOT NULL,
       ENTRY_DTCREAT_TYPE        SMALLINT NOT NULL,
       ENTRY_DTCREATED           FLOAT NOT NULL,
       ENTRY_DELIVERYID          CHAR(N2) NOT NULL,
       MAPPED_DNAME              CHAR(N3) NOT NULL,
       DISTHDR_RECIPIENT         CHAR(N4) NOT NULL,
       DISTHDR_RECIPCNT          SMALLINT NOT NULL,
       ROWLOCKED                 CHAR(1) NOT NULL,
       DISTHDR_RECPIENT          LONG VARCHAR FOR BIT DATA,
       DISTHDR_RECIPS            VARCHAR(N5) FOR BIT DATA NOT NULL
      );
  EXEC SQL CREATE UNIQUE INDEX OV2LAN.STINDX ON
OV2LAN.STATUS_CORRELATE
     ( ENTRY_USER, ENTRY_DELIVERYID, ENTRY_DTCREATED
     );
  EXEC SQL INSERT INTO OV2LAN.STATUS_CORRELATE
      (ENTRY_USER         ,
       ENTRY_DTCREAT_TYPE ,
       ENTRY_DTCREATED    ,
       ENTRY_DELIVERYID   ,
       MAPPED_DNAME       ,
       DISTHDR_RECIPIENT  ,
       DISTHDR_RECIPCNT   ,
...