HP Model 755/125cL HP-UX DMI 2.0 Developer's Guide: HP-UX/HP 9000 Computers, - Page 33

Writing Component MIF Files

Get HP Model 755/125cL - Workstation PDF manuals and user guides View all HP Model 755/125cL manuals
Add to My Manuals
Save this manual to your list of manuals

Page 33 highlights

4 Writing Component MIF Files Management Information Format (MIF) Files Within DMI, information about all components is defined in a language called the Management Interface Format (MIF) and stored by the DMI SP in a MIF database. Each component has a unique MIF file which describes its manageable characteristics. Each MIF file describes one, and only one component. However, there may be multiple instances of the component on a single system. When a management application or component instrumentation asks the SP to add a component, the SP compiles the associated MIF file containing schema description data, checks it for adherence to the DMI MIF format and installs it in the MIF database. The MIF database is then accessed when a management application asks the SP to list, get or set the attributes of installed components. During initialization, if the SP detects that the MIF database is corrupt it removes the MIF database and creates a new MIF database containing the SP MIF and any MIF files that have been installed into the /usr/dmi/mif/C directory. If component instrumentation installs MIF files into the MIF database without copying the MIF file to the /usr/dmi/mif/C directory, that component instrumentation is responsible for reinstalling its MIF file into the MIF database after the SP detects a corrupt database. The HP-UX DMI 2.0 Software Developer's Kit includes a Unix Standards Group Definition MIF and associated instrumentation (hpuxci), a software MIF and associated instrumentation (swci), the Service Provider MIF, as well as several example MIF files in the /usr/dmi/examples/ci directory. Each MIF file contains one, and only one component definition. The component definition has the following syntax: start component name = "component name" [description = " description string" ] [pragma = "pragma string" ] [component definition goes here] end component 33

  • 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
33
4
Writing Component MIF Files
Management Information Format (MIF) Files
Within DMI, information about all components is defined in a language
called the Management Interface Format (MIF) and stored by the DMI
SP in a MIF database. Each component has a unique MIF file which
describes its manageable characteristics. Each MIF file describes one,
and only one component. However, there may be multiple instances of
the component on a single system.
When a management application or component instrumentation asks
the SP to add a component, the SP compiles the associated MIF file
containing schema description data, checks it for adherence to the DMI
MIF format and installs it in the MIF database. The MIF database is
then accessed when a management application asks the SP to list, get
or set the attributes of installed components.
During initialization, if the SP detects that the MIF database is corrupt
it removes the MIF database and creates a new MIF database
containing the SP MIF and any MIF files that have been installed into
the /usr/dmi/mif/C directory. If component instrumentation installs
MIF files into the MIF database without copying the MIF file to the
/usr/dmi/mif/C directory, that component instrumentation is
responsible for reinstalling its MIF file into the MIF database after the
SP detects a corrupt database.
The HP-UX DMI 2.0 Software Developer's Kit includes a Unix
Standards Group Definition MIF and associated instrumentation
(hpuxci), a software MIF and associated instrumentation (swci), the
Service Provider MIF, as well as several example MIF files in the
/usr/dmi/examples/ci directory.
Each MIF file contains one, and only one component definition. The
component definition has the following syntax:
start component
name = "component name"
[description = " description string" ]
[pragma = "pragma string" ]
[component definition goes here]
end component