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

Management Application Provider Functions

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

Management Interface Functions Management Application Provider Functions Management Application Provider Functions This section describes the Management Application Provider Functions that a client must provide to receive indications. A management interface client receiving indications undergoes a role reversal where, in RPC terms, it becomes an indication delivery server. This DMI SP is a client of this interface. Indication Functions All indication functions have some information in common. All indication functions have an opaque handle returned to the application. This handle contains the SubscriberID attribute from the client's row in the SPIndicationSubscription table. Additionally, all indication functions have the sender's address which provides a mechanism for identifying the local or remote system that sent the indication. DmiComponentAdded() Notifies the subscribing node that a component has been added to the MIF database. DmiErrorStatus_t DMI_API DmiComponentAdded( /* [in] */ handle_t bind_handle, /* [in] */ DmiUnsigned_t handle, /* [in] */ DmiNodeAddress_t* sender, /* [in] */ DmiComponentInfo_t* info); DmiComponentDeleted() Notifies the subscribing node that a component has been deleted from the MIF database. DmiErrorStatus_t DMI_API DmiComponentDeleted( /* [in] */ handle_t bind_handle, /* [in] */ DmiUnsigned_t handle, /* [in] */ DmiNodeAddress_t* sender, /* [in] */ DmiId_t compId); DmiDeliverEvent() Delivers event data to a management application. DmiErrorStatus_t DMI_API DmiDeliverEvent( /* [in] */ handle_t bind_handle, /* [in] */ DmiUnsigned_t handle, /* [in] */ DmiNodeAddress_t* sender, /* [in] */ DmiString_t* language, /* [in] */ DmiId_t compId /* [in] */ DmiTimestamp_t* timestamp, /* [in] */ DmiMultiRowData_t* rowData); 82 Chapter 9

  • 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
82
Chapter 9
Management Interface Functions
Management Application Provider Functions
Management Application Provider Functions
This section describes the Management Application Provider Functions
that a client must provide to receive indications.
A management interface client receiving indications undergoes a role
reversal where, in RPC terms, it becomes an indication delivery server.
This DMI SP is a client of this interface.
Indication Functions
All indication functions have some information in common. All
indication functions have an opaque handle returned to the application.
This handle contains the SubscriberID attribute from the client's row in
the SPIndicationSubscription table. Additionally, all indication
functions have the sender's address which provides a mechanism for
identifying the local or remote system that sent the indication.
DmiComponentAdded()
Notifies the subscribing node that a component has been added to the
MIF database.
DmiErrorStatus_t DMI_API DmiComponentAdded(
/* [in]
*/ handle_t
bind_handle,
/* [in]
*/ DmiUnsigned_t
handle,
/* [in]
*/ DmiNodeAddress_t*
sender,
/* [in]
*/ DmiComponentInfo_t*
info);
DmiComponentDeleted()
Notifies the subscribing node that a component has been deleted from
the MIF database.
DmiErrorStatus_t DMI_API DmiComponentDeleted(
/* [in]
*/ handle_t
bind_handle,
/* [in]
*/ DmiUnsigned_t
handle,
/* [in]
*/ DmiNodeAddress_t*
sender,
/* [in]
*/ DmiId_t
compId);
DmiDeliverEvent()
Delivers event data to a management application.
DmiErrorStatus_t DMI_API DmiDeliverEvent(
/* [in]
*/ handle_t
bind_handle,
/* [in]
*/ DmiUnsigned_t
handle,
/* [in]
*/ DmiNodeAddress_t*
sender,
/* [in]
*/ DmiString_t*
language,
/* [in]
*/ DmiId_t
compId
/* [in]
*/ DmiTimestamp_t*
timestamp,
/* [in]
*/ DmiMultiRowData_t*
rowData);