BMC_Impact data class

The BMC_Impact class is the parent class of the hierarchy of data classes that define the different types of service model relationships. This class inherits slots from the root class CORE_DATA and the superclass MC_SM_RELATIONSHIP.

This topic contains the following information about the BMC_Impact superclass:

Default service model data classes

BMC_Impact class definition

The following figure shows the BAROC definition of the BMC_Impact superclass, which is located in the mc_sm_object.baroc file:

BMC_Impact class definition

MC_PUBLISH_DATA_CLASS : BMC_Impact ISA MC_SM_RELATIONSHIP
  DEFINES {
     AccountID : STRING;
     ReadSecurity : LIST_OF STRING;
     ShortDescription : STRING, default = 'na';
     WriteSecurity : LIST_OF STRING;
   };
END

BMC_Impact inherits slots from MC_SM_RELATIONSHIP, which is shown in the following figure. MC_SM_RELATIONSHIP is located in the mc_sm_root.baroc file.

MC_SM_RELATIONSHIP definition

MC_PUBLISH_DATA_CLASS:
MC_SM_RELATIONSHIP ISA MC_SM_DATA DEFINES
{
PropagationModel: STRING;
consumer_home_cell: STRING, parse=no, read_only=yes;
provider_home_cell: STRING, read_only=yes;
provider_classname: STRING;
State: MC_SM_RELATIONSHIP_STATE, default = ACTIVE;
StatusWeight : INTEGER, default=100;
consumer_id: STRING, key = yes, read_only=yes;
last_status_modification: INTEGER, parse=no, read_only=yes, representation = date;
propagated_status: MC_SM_COMPONENT_STATUS, parse=no, read_only=yes, default = UNKNOWN;
propagated_sub_status: MC_SM_COMPONENT_STATUS, parse=no, read_only=yes, default = UNKNOWN;
provider_id: STRING, key = yes, read_only=yes;
true_impact: MC_YESNO, parse=no, read_only=yes, default = NO;
change_number : INTEGER, parse=no, read_only=yes;
};
END

MC_SM_RELATIONSHIP inherits slots from MC_SM_DATA (which contains no slots, as shown in the following figure). MC_SM_DATA is located in the mc_sm_root.baroc file.

MC_SM_DATA definition

MC_DATA_CLASS:
MC_SM_DATA ISA CORE_DATA;
END

MC_SM_DATA inherits slots from CORE_DATA, which is shown in the following figure. CORE_DATA is located in the mc_root.internal.baroc file.

CORE_DATA definition

MC_DATA_CLASS :
  CORE_DATA
  DEFINES {
     data_handle : INTEGER, parse = no, read_only = yes;
     mc_udid : STRING, read_only = yes;
     mc_creation_time : INTEGER, parse = no, read_only = yes, representation = date;
     mc_modification_time : INTEGER, parse = no, read_only = yes, representation = date;
     mc_modification_requestor : STRING, parse = no, read_only = yes;
     publish_env_id : STRING, parse = no, read_only = yes;
   };
END

Relationship slot descriptions in alphabetical order

The following table alphabetically lists the slots that define CI relationships, with their descriptions and data type. The Source class column indicates the name of the class where the slot is defined.

BMC_Impact slot definitions in alphabetical order

Slot	Description	Data type or enumeration	Source class
consumer_id	mc_udid of the consumer CI	STRING	MC_SM_ RELATIONSHIP
change_number	Change number	INTEGER	MC_SM_ RELATIONSHIP
data_handle	Identifier in local cell	INTEGER	CORE_DATA
last_status_modification	Date/time when the value of true_impact function was last changed (used by GUI)	INTEGER	MC_SM_ RELATIONSHIP
mc_creation_time	Date and time when the object was created	INTEGER	CORE_DATA
mc_modification_time	Date and time when the object was last changed	INTEGER	CORE_DATA
mc_udid	Internal key used to reference the relationship; it is an inherited slot	STRING	CORE_DATA
propagated_status	Status that is currently propagated through the relationship	Enumeration: MC_SM_COMPONENT_ STATUS	MC_SM_ RELATIONSHIP
propagated_sub_status	Maximum of provider substatus and status values	Enumeration: MC_SM_COMPONENT_ STATUS	MC_SM_ RELATIONSHIP
PropagationModel	Name of the status propagation model used for determining the propagated status from of the provider's main status	STRING	MC_SM_ RELATIONSHIP
provider_classname	Name of the class of the provider CI	STRING	MC_SM_ RELATIONSHIP
provider_home_cell	The cell that receives events for the provider CI	STRING	MC_SM_ RELATIONSHIP
provider_id	mc_udid of the provider CI, the impacting CI	STRING	MC_SM_ RELATIONSHIP
State	State of the relationship, Active or Inactive. If Inactive, this relationship is not used for impact propagations.	Enumeration: MC_SM_RELATIONSHIP_STATE	MC_SM_ RELATIONSHIP
StatusWeight	Number that determines the degree of importance to give to each provider relationship that impacts a consumer CI	INTEGER	MC_SM_ RELATIONSHIP
true_impact	Flag indicating whether this relationship affects the impact_status of the consumer	Enumeration: MC_SM_YESNO	MC_SM_ RELATIONSHIP

BMC_Impact enumerations

The following enumerations are listed in the mc_sm_root.baroc file:

MC_SM_RELATIONSHIP_STATE
MC_SM_IMPACT_FUNCTION
MC_SM_SELF_FUNCTION
MC_SM_CO_FUNCTION
MC_SM_SLA_RESET_MODE
MC_SM_COMPONENT_SCOPE
MC_SM_COMPONENT_STATUS
MC_SM_SHADOW_REQUEST_OP
MC_SM_SLM_SLA_STATUS
MC_SM_CAUSE_TYPE
PRIORITY_FORMULA
MC_SM_SCHEDULE_STATUS
BMC_SIM_DOWNTIME_STATUS_CONFIG

BMC_Impact data class

BMC_Impact class definition

Relationship slot descriptions in alphabetical order

BMC_Impact enumerations

On this page