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

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

Component Interface Concepts Static vs. Dynamic Data set dynamic data. The shared library remains loaded for a period of time following the attribute access. The attributes that the SP gets and sets using the Overlay component instrumentation are also identified in the associated MIF file. The shared library must reside in /usr/dmi/overlay to run. Overlay component instrumentation is advantageous when the overhead to get or set attribute values is low, and the frequency for getting and setting attributes is low. However, with Overlay instrumentation event-generating attributes can not be programmed. Overlay component instrumentation is the preferred method for building component instrumentation. The conditions for which HP does not recommend using Overlay component instrumentation are when the MIF file defines event generating attributes and when the component defines large amounts of dynamic data. Ill-behaved Overlay components can crash the SP if they receive segmentation violations or perform illegal operations. The following example illustrates setting up a MIF Path statement and using the Path name as the value for each attribute that represents the dynamic data. For example: Start Path Name = "Overlay Component Instrumentation" Value = *"Overlay Component Instrumentation" Unix = "/usr/dmi/bin/overlayMemoryExample" End Path For additional information on creating MIF files, see the following chapter, Writing Component MIF Files. Chapter 3 29

  • 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
29
Component Interface Concepts
Static vs. Dynamic Data
set dynamic data. The shared library remains loaded for a period of
time following the attribute access.
The attributes that the SP gets and sets using the Overlay component
instrumentation are also identified in the associated MIF file. The
shared library must reside in /usr/dmi/overlay to run.
Overlay component instrumentation is advantageous when the
overhead to get or set attribute values is low, and the frequency for
getting and setting attributes is low. However, with Overlay
instrumentation event-generating attributes can not be programmed.
Overlay component instrumentation is the preferred method for
building component instrumentation. The conditions for which HP does
not recommend using Overlay component instrumentation are when
the MIF file defines event generating attributes and when the
component defines large amounts of dynamic data.
Ill-behaved Overlay components can crash the SP if they receive
segmentation violations or perform illegal operations.
The following example illustrates setting up a MIF Path statement and
using the Path name as the value for each attribute that represents the
dynamic data. For example:
Start Path
Name = "Overlay Component Instrumentation"
Value = *"Overlay Component Instrumentation"
Unix = "/usr/dmi/bin/overlayMemoryExample"
End Path
For additional information on creating MIF files, see the following
chapter, Writing Component MIF Files.