Custom dynamic attributes

Edit online

The RMC subsystem supports the definition of custom dynamic attributes within a resource class and their use in event expressions.

Custom dynamic attributes are run-time extensions to the resource dynamic attributes that are returned by the lsrsrcdef -ad resource_class_name command. Custom dynamic attributes are defined for each resource. The manner in which custom dynamic attributes are defined is a function of the resource class implementation. Custom dynamic attributes cannot be defined as class dynamic attributes.

Custom dynamic attributes are supported if the resource class defines the CustomDynamicAttributes persistent resource attribute. This persistent attribute is of type SD Array and contains one array element for each custom dynamic attribute that may be defined for the resource. For any given resource, if this persistent attribute has an array value with zero elements, custom dynamic attribute are not defined for the resource. This SD contains the following fields:
  • Name, which is the name of the custom dynamic attribute.
  • ID, which is the ID of the custom dynamic attribute.
  • DataType, which is the datatype of the custom dynamic attribute.

    Custom dynamic attributes cannot be a Structured Data type.

  • VariableType, which is the variable type of the custom dynamic attribute: Counter, Quantity, Quantum, or State. For more information about variable types, see Dynamic attributes.
  • ReportingInterval, which is the reporting interval of the custom dynamic attribute.
  • Properties, which are the properties of the custom dynamic attribute.

    One property is supported. If Bit 0 of the property value is set, the attribute must be monitored using an event expression in order to query its value using the lsrsrc command.

Each resource does not need to define the same custom dynamic attributes. However, when using the mkcondition command, all selected resource must have matching values for their CustomDynamicAttributes persistent resource attributes if any custom dynamic attributes are used in the event expressions. If the RMC subsystem cannot obtain the values of the CustomDynamicAttributes persistent resource attributes for the selected resources, the mkcondition command returns an error in its response, indicating that the custom dynamic attributes in the expressions could not be validated.