International Business Machines Corporation

Jeremy P Goodwin

Paul Joseph Reder

Wade C Allen

Robert Louis Nielsen

Douglas Toltzman

In an Open System Interconnection (OSI) environment, an agent Common Management Information Protocol (CMIP) platform maintains an up to date tree of all of the Managed Object Instances (MOIs), in order to perform scoping functions. The agent platform receives a message from an OSI manager which includes a base MOI and levels below the base MOI to receive the message. The agent platform recurses through the tree below the base MOI to determine which MOIs should receive the message. If the message is delete, the children of MOIs to be deleted are also deleted. The children of undeletable MOIs are not deleted. A current, accurate tree is maintained by the agent platform, which can register a new MOI in the tree when a valid request is received from the MOI or the manager. The agent platform can also deregister an MOI upon valid request from the agent associated with the platform.

Object independent scoping in an open system interconnection system

In a compiler for the GDMO language, a verified and ordered output list of GDMO templates is provided by a method that lists each template in the output list such that all listed templates are preceded in the list by templates that are referenced by a listed template.

Process for verifying GDMO template references and for providing an

Information on GDMO managed objects, including class hierarchy and the name binding templates, is compiled into a naming table. This naming table is built from an inheritance table and the name binding template information. The inheritance table indicates the inheritance hierarchy of the managed object classes. The compiler builds the inheritance table as a square matrix with a row and column for each class, and the classes arranged in an ordered list from highest to lowest in hierarchy. The compiler enters a one at each position in the inheritance table to indicate that the managed object class in the row inherits from the managed class in the column. With the inheritance table as a ready reference, the compiler builds the naming table from the name binding templates available as listed in the GDMO source files. The naming table is a square matrix identical to the inheritance table except the entries in the naming table are not ones and zeros. Instead, entries in the naming table are lists of name binding templates that may be used to instantiate a managed object instance in the row class under a managed object instance in the column class.

Compilation of information contained in GDMO name bindings

Managed Object Instances (MOIs) in a network of OSI computing systems are created, or deleted, without disrupting their interaction with other managed object instances. This is accomplished by a multi-phase commit process operation where in the first phase, a create or delete request is verified, and the CMIP platform places the created or deleted MOI on a pending list in the CMIP platform, along with information identifying the location of the MOI in a hierarchy of MOIs. In the second phase, the object being created or deleted is asked to accept, or reject, the request. The object responds saying that it accepts or rejects the request. If the request is acceptable, the CMIP platform finishes the object's connection to the tree hierarchy, or disconnects the object from the tree. Then the CMIP platform sends back a message to the object to acknowledge the creation of the object, or to tell the object to delete itself. Finally, the CMIP platform sends a request completion message to the manager.

Growing community of inventors

Raleigh, NC, United States of America

Jeremy P Goodwin