HP Visualize c160L HP-UX DMI 2.0 Developer's Guide: HP-UX/HP 9000 Computers, - Page 27

The following examples shows how the component instrumentation

Get HP Visualize c160L - Workstation PDF manuals and user guides View all HP Visualize c160L manuals
Add to My Manuals
Save this manual to your list of manuals

Page 27 highlights

Component Interface Concepts Static vs. Dynamic Data ID = 1 Description = "System Memory Group" Start Attribute Name = "Manufacturer" ID = 1 Description = "Manufacturer of this" "component." Access = Read-Write Storage = Common Type = String(64) Value = "Hewlett-Packard, Co." End Attribute ComponentID attributes 2-6 deleted for example clarity End Group End Component Dynamic data requires component instrumentation intervention. The values do not reside in the MIF database. The attribute values in the MIF file are place holders for the real attribute values. The following examples shows how the component instrumentation retrieves an attribute Names. The SP learns from the MIF database that the data is dynamic. It gets the data from the component instrumentation and passes it back to the management application. Start Component ComponentID group deleted for example clarity Start Group Name = "Names" ID = 2 Class = "DMTF|DevNames|2.0" Description = "DMTF Developers names.Direct" "Interface Version" Key=1 Start Attribute Name = "Index" ID = 1 Description = "Index into names table." Access = READ-ONLY Type = INTEGER Value = 1 End Attribute . . . Chapter 3 27

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
Chapter 3
27
Component Interface Concepts
Static vs. Dynamic Data
ID = 1
Description = "System Memory Group"
Start Attribute
Name = "Manufacturer"
ID = 1
Description = "Manufacturer of this”
“component."
Access = Read-Write
Storage = Common
Type = String(64)
Value = "Hewlett-Packard, Co."
End Attribute
// ===============================================
// ComponentID attributes 2-6 deleted for example clarity.
// ===============================================
End Group
End Component
Dynamic data requires component instrumentation intervention. The
values do not reside in the MIF database. The attribute values in the
MIF file are place holders for the real attribute values.
The following examples shows how the component instrumentation
retrieves an attribute Names. The SP learns from the MIF database
that the data is dynamic. It gets the data from the component
instrumentation and passes it back to the management application.
Start Component
.
.
.
//==================================================
// ComponentID group deleted for example clarity.
//==================================================
Start Group
Name = "Names"
ID
= 2
Class = "DMTF|DevNames|2.0"
Description = "DMTF Developers names.Direct”
“Interface Version"
Key=1
Start Attribute
Name
= "Index"
ID
= 1
Description = "Index into names table."
Access = READ-ONLY
Type
= INTEGER
Value
= 1
End Attribute
.
.
.