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

Service Provider Functions for Management, Applications

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

Management Interface Functions Service Provider Functions for Management Applications Service Provider Functions for Management Applications Management applications must register with the DMI Service Provider. The following functions provide this capability. These calls contain fields which rarely change between a manager and a client. Initialization Functions DmiGetConfig() Retrieves the per-session string describing the current language in use. DmiErrorStatus_t DMI_API DmiGetConfig ( /* [in] */ DmiHandle_t handle, /* [out] */ DmiString_t** language); DmiGetVersion() Retrieves information about the SP's specification level and the MIF file types supported. DmiErrorStatus_t DMI_API DmiGetVersion( /* [in] */ DmiHandle_t handle, /* [out] */ DmiString_t** dmiSpecLevel, /* [out] */ DmiString_t** description, /* [out] */ DmiFileTypeList_t** fileTypes); DmiMainLoop() Waits on the socket communication thread for component instrumentation or the Indication Server thread for management applications. int DmiMainLoop() DmiRegister() Provides the management application or direct component instrumentation with a unique per-session handle. The SP uses this procedure to initialize its internal state for subsequent calls. Local use only. DmiErrorStatus_t DMI_API DmiRegister( /* [out] */ DmiHandle_t* handle); DmiRemoteRegister() Provides a unique per-session handle. The SP uses this procedure to initalize its internal state for subsequent calls to the remote node. DmiErrorStatus_t DMI_API DmiRemoteRegister( 76 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
76
Chapter 9
Management Interface Functions
Service Provider Functions for Management Applications
Service Provider Functions for Management
Applications
Management applications must register with the DMI Service Provider.
The following functions provide this capability. These calls contain
fields which rarely change between a manager and a client.
Initialization Functions
DmiGetConfig()
Retrieves the per-session string describing the current language in use.
DmiErrorStatus_t DMI_API DmiGetConfig (
/* [in]
*/
DmiHandle_t
handle,
/* [out] */
DmiString_t**
language);
DmiGetVersion()
Retrieves information about the SP's specification level and the MIF file
types supported.
DmiErrorStatus_t DMI_API DmiGetVersion(
/* [in]
*/ DmiHandle_t
handle,
/* [out] */ DmiString_t**
dmiSpecLevel,
/* [out] */ DmiString_t**
description,
/* [out] */ DmiFileTypeList_t**
fileTypes);
DmiMainLoop()
Waits on the socket communication thread for component
instrumentation or the Indication Server thread for management
applications.
int DmiMainLoop()
DmiRegister()
Provides the management application or direct component
instrumentation with a unique per-session handle. The SP uses this
procedure to initialize its internal state for subsequent calls. Local use
only.
DmiErrorStatus_t DMI_API DmiRegister(
/* [out] */ DmiHandle_t*
handle);
DmiRemoteRegister()
Provides a unique per-session handle. The SP uses this procedure to
initalize its internal state for subsequent calls to the remote node.
DmiErrorStatus_t DMI_API DmiRemoteRegister(