DmiRegisterCnf

On return from the DmiRegisterCiInd call, the service layer places a DmiRegisterCnf block in the response buffer. This block is the same as that described in DmiRegisterCnf Command Block.

The format for the command block is: ┌──────────────────────────────────────────────────────────────────────────────┐
│ Table 46. DmiRegisterCnf Command Block │
├───────────────┬───────────────┬───────────────┬──────────────────────────────┤
│ OFFSET │ SIZE │ TYPE │ VARIABLE NAME │
├───────────────┼───────────────┼───────────────┼──────────────────────────────┤
│ 0 │ 8 │ STRUCT │ DmiVersion │
├───────────────┼───────────────┼───────────────┼──────────────────────────────┤
│ 8 │ 4 │ INT │ iDmiHandle │
└───────────────┴───────────────┴───────────────┴──────────────────────────────┘

Variable Name

Variable Description
DmiVersion
A block defining the version of the service layer.
iDmiHandle
Set to a unique handle for this component instrumentation. This is only valid for as long as the component instrumentation is registered with the service layer. The handle is passed to the service layer when unregistering.

A component can register more than once. This is necessary when a component has multiple entry points for instrumentation. In this case, the component instrumentation is assigned multiple handles.

Processing DmiRegisterCnf displays an example of how to handle the DmiRegisterCnf callback command block. For this example, all callbacks that are returned to the management application are processed through a single entry point.

---

[Back: DmiRegisterCiInd]
[Next: DmiUnregisterCiInd]