Abstract: A code translator, constructed similar to a compiler, accepts as an input to be translated the assembly code written for one architecture (e.g., VAX), and produces as an output object code for a different machine architecture (e.g., RISC). The input code is converted into an intermediate language, and a flow graph is constructed. The flow graph is referenced by a flow analyzer for recognizing certain architecture-specific and calling standard-specific coding practices or idioms that cannot be automatically converted, particularly relating to stack usage, register usage, condition codes, and passing arguments for procedure calls. By tracking stack usage within routines, the compiler can distinguish up-level stack and return address references from valid local references. Also, it can inform the user of stack misalignment, which has a severe performance penalty, and can detect code segments where different flow paths may result in different stack depths at runtime, which may indicate a source code error.

Abstract: Multimedia data in an object structure include entity objects and relation objects, wherein each entity object has data representing a media element as internal data, and each relation object represents a relation between the entity objects. A relation object is searched according to information specified by a search command, and a searched relation object and internal data of an entity object related thereto are displayed on the screen of a display unit as a set of display elements. To generate a digest of the multimedia data, a matching between a structure portion of a user model and a structure portion of a system model is examined. The user model is generated according to a request of the user and arranged in layers, while the system model has been previously generated. The multimedia data are arranged in layers according to the importance of respective data elements constituting the multimedia data.

Abstract: The present invention includes an approach to index tree structure changes which provides high concurrency while being usable with many recovery schemes and with many varieties of index trees. The present invention permits multiple concurrent structure changes. In addition, all update activity and structure change activity above the data level executes in short independent atomic actions which do not impede normal database activity. Only data node splitting executes in the context of a database transaction. This feature makes the approach usable with diverse recovery mechanisms, while only impacting concurrency in a modest way. Even this impact can be avoided by re-packaging the atomic actions, at the cost of requiring more from the recovery system.

Abstract: In a distributed computer network having a large number of intercommunicating distributed nodes and a smaller number of control nodes in which each distributed node reports status information to a particular one of the control nodes, a method is provided for guaranteeing that at least one control node receives a status message from a distributed node despite the unavailability of the particular control node to which the distributed node normally sends its status messages. Each distributed node associates a serial number and time stamp and an identification of itself with each message it originates, and each distributed node retains copies of the messages. Should a distributed node be unsuccessful in transmitting to its normal control node it attempts to transmit to other control nodes until it transmits successfully.

Abstract: A method and object-oriented architecture for interfacing a user to a relational database system The contour of the interface is defined by a profile object and a task object. The profile object, in response to user selection, defines one of multiple role objects with associated user proficiency and system behavioral characteristics. The task object responds to parameters derived from the profile object to generating a query for the relational database system. In one form, the task object includes one or more functional objects suitable to query the database. Representative functional objects are the domain object (used to formulate problem oriented queries), the analysis object (used to analyze the data extracted from the database), the report object (used to generate a user response format), and the link object (used to relate the components within the task object).

Abstract: A method is disclosed for concurrency control in a system having both pessimistic and optimistic transactions, comprises the steps of entering locks on objects both for optimistic and pessimistic transactions, and validating an optimistic transaction at commit time by checking that all objects on which said optimistic transaction holds a lock have not become obsolete during the execution of said optimistic transaction. Further, a system is shown enabling optimistic and pessimistic transactions to coexist, comprising a lock table into which locks are entered for both optimistic and pessimistic transactions, a wait queue in which pessimistic transactions are entered to wait for locks held by either optimistic or pessimistic transactions, a conflict table which is referenced to determine if a lock held by a first transaction is a conflict lock with respect to a lock requested by a second transaction, and code connected to the lock table, wait queue, and conflict table.

Abstract: An installation creates a source I/O definition file (IODF), defining a current system I/O configuration, and a target IODF, defining a future I/O configuration. An activate function is initiated to change the system's hardware and software definition to correspond to the target IODF. A compare function compares the source and target IODFs, and creates a Configuration Change Block (CCB) to efficiently drive the change process. A validation function validates that the proposed change is valid, and the change process updates the hardware and software configuration definitions. If the change process is successful, a notification is sent; if not, a back-out process restores the I/O configuration to its initial state.

Abstract: A personal communicating computer (112) (FIG. 1) remains in contact, via a wireless network, with an office server (101). Documents from various sources can be transmitted to the personal communicating computer (112) using this network. Upon receipt, such documents can be accessed and utilized in a variety of ways. In particular, such documents can be annotated in a variety of ways, and those annotations forwarded on to other destinations for appropriate review and handling.