International Business Machines Corporation

Jonathan David Champlin

John Douglas Curtis

Gary Paul Rheaume

Michael R O'Brien

Margo L Ezekiel

Thomas M Bentley

Arthur H Thomas

A system that persistently maintains and exposes one or more previous object hierarchies to which an object belonged across one or more hierarchy destroying operations, such as operations that delete parent objects, add parent objects subsequent to addition of their descendent objects, forward objects to or from the hierarchy, and/or modify hierarchy determining rules. A user interface object allows user access to one or more persistent hierarchies for the corresponding object. A hierarchy list or the like allows a user to select a desired one of the persistent hierarchies. A persistent hierarchy can be accessed in the disclosed system through a display object associated with any object within the hierarchy, including the root, leaves, and any intervening objects. When objects are deleted, 'ghost' objects are maintained and displayed to the user in the hierarchical positions of the deleted objects when a persistent hierarchy is displayed.

Persistent object linkage using ghosting

Unique identifiers referred to as 'keys' are generated for objects stored on each node. When a container object including at least one embedded object is transferred from a sending node to a receiving node, the sending node sends the key uniquely identifying the embedded object to the receiving node to determine whether the embedded object is already stored on the receiving node. If the receiving node indicates that the embedded object is already stored at the receiving node, then the sending node determines that the embedded object does not need to be sent to the receiving node. In that case, if the embedded object has not been sent, the sending node does not send the embedded object. If the sending node has already started sending the embedded object, then the sending node terminates sending of the embedded object.

Preventing transfer and duplication of redundantly referenced objects across nodes of an application system

A method of diagnosing a fault condition within software can include, responsive to a fault condition within a computing system belonging to an organization, automatically sending call-stack information for the fault condition to a first server within the organization. Within the first server, the call-stack information for the fault condition can be compared with call-stack information from prior fault conditions that occurred within the organization to determine whether the call-stack information for the fault condition matches call-stack information from one of the prior fault conditions. The method further can include sending the call-stack information to a second server for comparison with call-stack information from prior fault conditions that occurred within at least one different organization if the call-stack information for the fault condition does not match.

Call-stack pattern matching for problem resolution within software

Multiple subroutines in one program, or a series of programs provide centralized network administration. The administrative program monitors communications software for consistency at both server and client locations, monitors logs, objects and files at server and/or client locations and assures that investigative measures be undertaken, either by providing automatic updates or by flagging monitored features for administrative follow-up.

Growing community of inventors

Cold Spring, NY, United States of America

Jonathan David Champlin