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

Table 4-1, Definitions Contained in a MIF File, Definition, Purpose, Path Definitions, Enum Definitions

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 34 highlights

Writing Component MIF Files Management Information Format (MIF) Files In addition, a MIF file contains some of the following definitions: Table 4-1 Definitions Contained in a MIF File Definition Purpose Path Definitions Locate files used to manage the component. There may be one path definition for each callable function. Enum Definitions Allow strings to be associated with 32-bit integers. There may potentially be one enum definition for each enumeration list. Group Collection of one or more attributes, arranged into logical Definitions sets. There must be one group called ComponentID. There may be zero to many additional groups. Pragma Provides additional information about the component, Statements group or attribute. Attribute Provides data about the data, and is contained within Statements the group statement. Each group must have at least one attribute statement. Every component MIF must contain a ComponentID group with ID 1. This group provides the base-level identification of the component and represents the minimum amount of information that a component developer should provide. The ComponentID class string is "DMTF|ComponentID|001". The six named attributes of the group are Manufacturer, Product, Version, Serial Number, Installation, and Verify. Refer to http://www.dmtf.org for conformance requirements. 34 Chapter 4

  • 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
34
Chapter 4
Writing Component MIF Files
Management Information Format (MIF) Files
In addition, a MIF file contains some of the following definitions:
Every component MIF must contain a ComponentID group with ID 1.
This group provides the base-level identification of the component and
represents the minimum amount of information that a component
developer should provide.
The ComponentID class string is “DMTF|ComponentID|001”. The six
named attributes of the group are Manufacturer, Product, Version,
Serial Number, Installation, and Verify. Refer to http://www.dmtf.org for
conformance requirements.
Table 4-1
Definitions Contained in a MIF File
Definition
Purpose
Path Definitions
Locate files used to manage the component. There may
be one path definition for each callable function.
Enum Definitions
Allow strings to be associated with 32-bit integers. There
may potentially be one enum definition for each
enumeration list.
Group
Definitions
Collection of one or more attributes, arranged into logical
sets. There must be one group called ComponentID.
There may be zero to many additional groups.
Pragma
Statements
Provides additional information about the component,
group or attribute.
Attribute
Statements
Provides data about the data, and is contained within
the group statement. Each group must have at least one
attribute statement.