CIM indications

Indications in CIM are represented as instances of class CIM_Indication. This abstract class serves as the base class for all indication classes.

Indications are transient instances used to distribute information from an indication generator to an arbitrary number of indication consumers. Therefore, they are typically very short-living. Indications have a source namespace, this is the value of the SourceNamespace property of the CIM_IndicationFilter instance that produced the indication. Although indications are instances of CIM classes, they are unique in that they cannot be addressed, but can only be received by subscription. Hence, indication instances cannot be enumerated, created, deleted, retrieved or modified by client operations.

Note that z/OS does not ship generic providers, that is, an indication subscription is only processed if the required indication provider exists and is registered with the CIM server for a certain CIM resource class.

The CIM Schema version provided with z/OS® supports two types of indications (representing different types of events) which are modeled as CIM_Indication subclasses. These subclasses include:

CIM_InstIndication

used to report life cycle events for CIM instances. Types of events include: Instance creation, deletion, modification, method invocation and read access. For each of these types, a specific subclass of CIM_InstIndication is defined in the CIM Schema: CIM_InstCreation, CIM_InstDeletion, CIM_InstModification, CIM_InstMethodCall and CIM_InstRead. Only the first three are currently supported for z/OS.

CIM_ProcessIndication

used to report the occurrence of any other event, typically alert type events. See CIM_ProcessIndication.

Figure 18. z/OS CIM indication hierarchy