Setting up DFSMSrmm common information model (CIM) provider

A plug-in adapter created for the OpenPegasus CIM environment supports removable media. This Java class maps DFSMSrmm resources into those defined in the CIM object model. This plug-in adapter uses the CIM provider interface to provide real-time information about storage resources.

Requirement: For operation of the DFSMSrmm CIM provider under Linux, a fully functional web service as well as an xmlCIM compliant product that supports Java, such as the OpenPegasus C++ CIM server from the OpenGroup, is required to use the DFSMSrmm CIM provider. The required release of the OpenPegasus package is 2.8.0 or above and is available at:

http://www.openpegasus.org

Please refer to the OpenPegasus documentation on how to install and configure the CIM server under Linux.

For operation under z/OS, the OpenPegasus CIM server package is pre-installed within the file system of the UNIX System Services. The CIM server must be fully configured before the DFSMSrmm CIM provider can make use of it. See z/OS Common Information Model User's Guide on how to setup the CIM server. Ensure that you perform all the RACF security steps in advance, before attempting to run the CIM provider against the CIM server.

To use SLP and set up the DFSMSrmm CIM agent for use by TPC or another application supporting SMI-S, you must configure OpenPegasus to enable SLP.

The CIM server runs either on a non-z/OS server, or directly on z/OS. The CIM client/browser runs on any platform supported by the provider of that client or application.

The DFSMSrmm Common Information Model (CIM) provider application programming interfaces are Java classes that implement the CIM-specified methods required of providers. The CIM-classes provided by DFSMSrmm and the providers for those classes are defined in a Managed Object Format (MOF) file. Each of the classes are subclasses of a corresponding class of the CIM schema version 2.17, respectively SMI-S 1.1.

The DFSMSrmm CIM agent now has an option to register itself using the SMI-S Storage Library profile so that storage management clients (and TPC in particular) can use Service Location Protocol (SLP) to detect the CIM agent and determine the registered profiles that it can support. The registration of the profile is performed by binding an instance of a subclass of the CIM_RegisteredProfile class to all managed instances of CIM_ComputerSystem subclasses. OpenPegasus provides its own implementation of the SMI-S Server profile and the engine for the binding of the vendor CIM classes and the profiles they correspond to.

The CIM server reads and interprets the MOF file and calls the providers, as required. The DFSMSrmm-provided classes extend those of the standard CIM object model and enable DFSMSrmm to provide information about removable media managed by DFSMSrmm in real time.

These DFSMSrmm CIM classes are supported:

IBMRMM_PhysicalVolume
IBMRMM_LogicalVolume
IBMRMM_Dataset
IBMRMM_Owner
IBMRMM_Location
IBMRMM_ShelfLocation
IBMRMM_Product
IBMRMM_PolicyRule
IBMRMM_Control
IBMRMM_ChangerDevice
IBMRMM_Manufacturer
IBMRMM_SCSIProtocolController
IBMRMM_SoftwareIdentity
IBMRMM_TapeDrive
IBMRMM_TapeLibrary
IBMRMM_PhysicalLogicalVolume (association 1:1)
IBMRMM_LogicalVolumeDataset (association 1:N)
IBMRMM_LogicalVolumeOwner (association N:1)
IBMRMM_PhysicalVolumeCurrentLocation (association N:1)
IBMRMM_PhysicalVolumeDestinationLocation (association N:1)
IBMRMM_PhysicalVolumeHomeLocation (association N:1)
IBMRMM_PhysicalVolumeLoanLocation (association N:1)
IBMRMM_PhysicalVolumeOldLocation (association N:1)
IBMRMM_PhysicalVolumeRequiredLocation (association N:1)
IBMRMM_PhysicalVolumeCurrentShelfLocation (association 1:1)
IBMRMM_PhysicalVolumeDestinationShelfLocation (association 1:1)
IBMRMM_PhysicalVolumeOldShelfLocation (association 1:1)
IBMRMM_DatasetOwner (association N:1)
IBMRMM_LogicalVolumeChainedLogicalVolume (association 1:1)
IBMRMM_LogicalVolumeLogicalVolumeInChain (association 1:N)
IBMRMM_LocationShelfLocation (association 1:N)
IBMRMM_ProductLogicalVolume (association 1:N)
IBMRMM_PolicyRuleNextPolicyRule (association N:1)
IBMRMM_PolicyRuleAndPolicyRule (association N:1)
IBMRMM_PolicyRulePolicyRuleInChain (association 1:N)
IBMRMM_PolicyRuleLocation (association N:1)
IBMRMM_PolicyRuleOwner (association N:1)
IBMRMM_ChangerDeviceController (association N:M)
IBMRMM_ChangerDeviceSoftware (association N:M)
IBMRMM_LocationManufacturer (association N:1)
IBMRMM_TapeLibraryLocation (association 1:N)
IBMRMM_TapeDriveController (association N:M)
IBMRMM_TapeDriveSoftware (association N:M)
IBMRMM_SearchOperands (aux class for search type operations)
IBMRMM_DeleteOperands (aux class for delete type operations)

LIST, SEARCH, ADD, CHANGE, and DELETE-type operations are fully supported by the providers for all classes. Each CIM class is served by its own provider Java class.

The subclasses created for the DFSMSrmm-managed media have all of the attributes of the CIM classes from which they are derived. In addition, they contain additional attributes that are mapped to those of the resources under DFSMSrmm control. The elements and their attributes, defined in the XML schema for the DFSMSrmm application programming interface, are mapped and converted to the attributes in the DFSMSrmm CIM classes.

Figure 1 shows a picture of the elements involved in the Common Information Model (CIM). The CIM client is the CIM browser that allows you to view information about the resources managed by the CIM server. Other CIM-compliant clients can also be used as CIM browsers. Each CIM server maintains a repository of persistent information for managed resources, but also retrieves information in real-time using the provider interface associated with other managed resources. The DFSMSrmm provider uses the DFSMSrmm application programming interface through the DFSMSrmm Web service or direct function call to retrieve information about DFSMSrmm resources in real-time.

Figure 1. Example of DFSMSrmm common information model (CIM) This is a picture of the elements involved in the Common Information Model (CIM), which include the CIM client (CIM browser) and CIM servers (DFSMSrmm COM providers).

This is a picture of the elements involved in the Common Information Model (CIM), which include the CIM client (CIM browser) and CIM servers (DFSMSrmm COM providers).