Abstract: SVE management software uses management software running at a central service processor to control storage virtualization engines operating in a plurality application programming interface (API) that allows a consistent control of all SVE facilities by means of a set of API commands. The management software controls a dispatch module that translates the commands into appropriate instructions for the SVE nodes and communicates with the remote SVE nodes by a plurality of node client-node server pairs that transfer instructions from the dispatch module to the remote nodes and transfer requested information back from the remote nodes to the dispatch module. Various interfaces, such as a command line interpreter and a CIM provider can be built using the API commands.

Abstract: SVE management software uses management software running at a central service processor to control storage virtualization engines operating in a plurality of remote SVE nodes via remote method calls. The management software provides an application programming interface (API) that allows a consistent control of all SVE facilities by means of a set of API commands. The management software controls a dispatch module that translates the commands into appropriate instructions for the SVE nodes and communicates with the remote SVE nodes by a plurality of node client-node server pairs that transfer instructions from the dispatch module to the remote nodes and transfer requested information back from the remote nodes to the dispatch module. Various interfaces, such as a command line interpreter and a CIM provider can be built using the API commands.

Abstract: Information concerning CIM classes and instances used to model a managed system is stored in two hash tables that are built at runtime when instances are added to the system. The first hash table, called a subclass table, identifies the subclasses of each CIM class. The second hash table, called an instance table, identifies the instances in the system for each class. The instance and subclass tables are used to retrieve information concerning the CIM instances. In particular, the instance table is used to retrieve all instances of a particular class and the subclass table is used to determine which classes to examine for instances. In one embodiment, the instance table is a hash table that contains a plurality of hash tables. The first hash table, called the primary instance table, contains key-value pair entries, in each entry the key is a CIM class and the value is a secondary hash table that contains the instances of that CIM class. The secondary hash table also contains key-value pair entries.