International Business Machines Corporation

Robert L Abraham

Floyd W Shackelford

Richard E Moore

William L Rich

Richard S Briggs, Jr

John R Tiller, Jr

Herman Mitchell

Michael P Priven

Cynthia A Ross

Badari N Panuganti

Laura A Stowers

Thomas P Moorman

James Richard Wason

Christopher Jonathan Davis

Charles B Harvey, Jr

April D Stiles

Adrienne Tin

Scott Kelly Hayward

Teresa E Merrick

Jane E Schrock

Vincent J Osisek

A system and method for measuring the value of elements in an information repository includes, in one embodiment, various methods of measuring the value of elements in an information repository are provided. Knowing which elements in the repository are most used may define one measure of their value. This may serve a number of business purposes including, for example, establishing how to price those assets if they are sold; identifying which assets are candidates for further investment; assessing the performance of the information developers who created them; deciding which assets should be retired from the repository; and measuring the level of asset reuse in an organization.

System and method for measuring the value of elements in an information repository

The security of data elements which represent an industrial process, which are manipulated by users on a data processing system and in which the industrial process includes a series of industrial process steps, are controlled by permitting groups of users to access predetermined data elements based on the industrial process step at which the industrial process is currently active. A user is prevented from accessing the requested element if the industrial process is not at an industrial process step corresponding to one of the industrial process steps for which the user has authority to access the data element. Thus, access to data is prevented based on the status of the data, in addition to the type of data. When selected database elements are associated with one of many locations, access is also denied to a user based on the location. Security access based on status and location may be provided in response to a change in the current industrial process step. Access authority to the data elements is changed compared to the access authority at the immediately preceding industrial process step based on mappings in one or more tables. Improved security of data elements which represent an industrial process is thereby provided.

Method and apparatus for controlling access to data elements in a data

Objects import data from, and export data to, a plurality of external systems in an object oriented computing system via a uniform external interface. The uniform interface includes external interface layers and internal interface layers. Each external interface layer converts data from the associated external system into an identifying token and data value. The external layer also converts an identifying token and data value into data which is formatted for the associated external system. The internal interface layer accepts an identifying token and data value from the external interface layer and converts the data value to a data attribute associated with an object. The internal interface layer also converts a data attribute into an identifying token and data value and provides the token and data value to the external interface layer. Thus, objects need only communicate with the internal interface layer in order to import and export data. The external interface layer includes customized conversion routines for converting a token and data value to data which is useable by an external system. Data validation and storage takes place via the internal interface layer. Accordingly, replication of code is minimized and the complexity of the object oriented system is reduced.

System for providing a uniform external interface for an object oriented

Data may be manipulated directly in an object oriented programming system by providing a slot object which contains data within its frame. In contrast with conventional objects, the frames of which only contain attributes of the associated instances, the slot object contains actual data therein. Since this data is not contained in a separate object, a unique object identified need not be provided, thus simplifying object management. Unique messages also need not be provided so that message overhead is simplified. Memory fragmentation is also reduced because simple and tightly bound data may be encapsulated within a larger slot object. The data area in the slot object may be of fixed or variable size.

Slot objects for an object oriented programming system

In an Object Oriented Programming System, a Communications Interface Packet (CIP) enables processing in either a remote system or in a batch environment. A CIP is an object in an Object Oriented Programming System, and like any other object, the CIP object contains data or attributes surrounded by or encapsulated by methods or actions for those data or attributes. Unique to a CIP, however, are attributes which contain an action, an object and parameters. An Application Programming Interface (API) method enables remote processing. An IPA method, which is the reverse of the API method, creates the CIP object which is to be executed in a remote or batch system through the application programming interface. After a CIP object has been created, it must be flattened or formatted prior to submission to the batch system or prior to sending the CIP object to a remote system. Flattening or formatting puts the CIP object into a flat sequential file known as a product data interface (PDIF) file for use by either the remote or batch system. The PDIF file includes three major sections known as the administrative header section, the data dictionary section, and the object data section.

Remote and batch processing in an object oriented programming system

A method and system for dynamically controlling the horizontal scrolling of data contained in a stored table of arbitrary size in a windowing environment. The list of data to be scrolled through is stored in memory with certain columns designated as sticky. Responsive to input from the user, a process is invoked to either scroll left or right through data contained in the stored list. A 'must display' column is determined based on the current display in the window and the direction of scrolling. The sticky columns that can fit with the 'must display' column are determined and placed on the display. Sticky columns that cannot be placed on the display with the 'must display' column due to window size limitations are temporarily suppressed. Additional non-sticky columns are placed on the display on a space-available basis including the placement of a partial column that fills the display.

System and method for dynamic control of horizontal scrolling

A Unit of Work object class for an object oriented database management system provides concurrent processing through Unit of Work levels and instances while maintaining the integrity of the data in the database. Each new Unit of Work assigned to a task is an instance of the Unit of Work object class. A Unit of Work manager controls each step such that manipulation of the data occurs to the copies at that particular level for that particular instance. Only after all levels have been completed satisfactorily will a 'Commit' occur to the data in the database. If completion is not satisfactory, Rollback of the levels occur, thus preserving data integrity. The Unit of Work manager can also switch control between Unit of Work instances, thus permitting simultaneous performance of tasks.

Unit of work for preserving data integrity of a data-base by creating in

A data structure and method for uniquely identifying, and optimizing access to, object instances in an object oriented programming environment on a data processor containing a memory. Objects are categorized into one or more classes which define the method of the categorized objects, and messages are sent by the data processor to objects to perform actions. The data structure consists of a persistent portion containing a unique object identifier and a non-persistent portion containing the access address of an instance data frame in memory. The access address is set to the address of the instance data frame control block when the message is sent in order to optimize subsequent messages to the same object instance. The instance data frame control blocks are not allocated in memory until a first message is sent to an instance.

System for persistent and delayed allocation object reference in an

A system for implementing a messenger and object manager in an object oriented programming environment on a data processor containing a memory, in which objects are categorized into one or more classes which define methods of the objects categorized therein, and in which messages are sent by the data processor to objects to perform actions thereon. The system includes a message call processing procedure operating on the data processor for processing message calls to instances, including a method resolution segment for calling a loaded classes table to determine whether the class corresponding to a method of the instance is loaded, where the method corresponds to the action requested by the message. If the corresponding class is not loaded in main memory, then the system dynamically loads the class. A data resolution segment calls an object management table to resolve an indirection pointer which points to the address of a data frame corresponding to the instance.

System and method for implementing a messenger and object manager in an

A persistent data interface for an object oriented programming system provides a persistent class object. Any object which must survive a run time session is arranged to inherit from the persistent class object. Any object which inherits from the persistent class automatically becomes a persistent object. The persistent class includes a 'materialize' method for automatically retrieving a persistent object from nonvolatile memory and placing it in volatile memory if the persistent object cannot be located in volatile memory. A 'dematerialize' method is also included for removing an object from volatile memory and storing it in nonvolatile memory. Data integrity of the system is thereby preserved.

Persistent data interface for an object oriented programming system

Time consuming and reusable queries are handled in an object oriented database management system by providing a persistent stream object class. The persistent stream object class is a subclass of the stream class which is typically provided to encapsulate the results of a query. The persistent stream class inherits all the attributes and methods of the stream class but also includes a 'save' method for saving the results of a query. When a query names a persistent stream as it object, the query results are saved. The query may also be performed in background or batch mode. All time consuming and reusable queries are performed by sending a query message to the persistent stream class, to thereby automatically save the query results.

Persistent stream for processing time consuming and reusable queries in

A resumeable batch query object class provides a link between a first dialog for obtaining information regarding a query to be performed by an object oriented database management system, a second dialog for manipulating the results of the query, and the stream which includes the query results. The resumeable batch query attributes include identifiers of the second dialog and the stream, and a method to run the query. The resumable batch query is used by the object oriented database management system to allow a second dialog to manipulate results of a batch or background query in the same manner as results of a foreground or interactive query. Time consuming queries may thereby be processed in background mode in a manner which is transparent to the second dialog.

Resumeable batch query for processing time consuming queries in an

The present invention is directed to systems and methods for recovering from unplanned failures in object oriented computing environments. The systems and methods of the present invention recover from unplanned failures in an efficient manner by storing recovery information in recovery objects. During recovery operations from an unplanned failure, object instance methods (which were abnormally terminated by the unplanned failure) use the recovery information to identify committable actions which were executed prior to the unplanned failure. The object instance methods then execute committable actions which were not executed prior to the unplanned failure. Thus, according to the present invention, the committable actions which were executed prior to the unplanned failure are not re-executed, and the committable actions which were not executed prior to the planned failure are executed.

Growing community of inventors

Marietta, GA, United States of America

Robert L Abraham