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

Service Provider Functions for Components

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

Component Interface Functions Service Provider Functions for Components Service Provider Functions for Components Using the following Service Provider Functions for Components, component instrumentation code can register with the SP to override its current access mechanism for the registered attributes. Instead of manipulating the data in the MIF database or invoking programs, the SP calls the entry points provided in the registration call. Once the component unregisters, the SP returns to its normal method of processing requests for the data as defined in the SP's MIF. In this manner, component instrumentation temporarily interrupts normal processing to perform special functions. • "DmiMainLoop()" on page 42 • "DmiOriginateEvent()" on page 42 • "DmiRegisterCi()" on page 43 • "DmiUnregisterCi()" on page 43 DmiMainLoop() Waits on the socket communication thread for component instrumentation or the Indication Server thread for management applications. int DmiMainLoop() DmiOriginateEvent() Originates an event for filtering and delivery. This function performs any necessary indication filtering (or subsequent processing) prior to forwarding the event to the registered management applications. DmiErrorStatus_t DMI_API DmiOriginateEvent( /* [in] */ DmiId_t componentId, /* [in] */ DmiString_t * language, /* [in] */ DmiTimestamp_t * timestamp, /* [in] */ DmiRowData_t * rowData); 42 Chapter 6

  • 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
42
Chapter 6
Component Interface Functions
Service Provider Functions for Components
Service Provider Functions for Components
Using the following Service Provider Functions for Components,
component instrumentation code can register with the SP to override
its current access mechanism for the registered attributes. Instead of
manipulating the data in the MIF database or invoking programs, the
SP calls the entry points provided in the registration call. Once the
component unregisters, the SP returns to its normal method of
processing requests for the data as defined in the SP's MIF. In this
manner, component instrumentation temporarily interrupts normal
processing to perform special functions.
•
“DmiMainLoop()” on page 42
•
“DmiOriginateEvent()” on page 42
•
“DmiRegisterCi()” on page 43
•
“DmiUnregisterCi()” on page 43
DmiMainLoop()
Waits on the socket communication thread for component
instrumentation or the Indication Server thread for management
applications.
int DmiMainLoop()
DmiOriginateEvent()
Originates an event for filtering and delivery. This function performs
any necessary indication filtering (or subsequent processing) prior to
forwarding the event to the registered management applications.
DmiErrorStatus_t DMI_API DmiOriginateEvent(
/* [in] */ DmiId_t
componentId,
/* [in] */ DmiString_t
*
language,
/* [in] */ DmiTimestamp_t
*
timestamp,
/* [in] */ DmiRowData_t
*
rowData);