HP 800 HP DLPI Programmer's Guide - Page 92

Dl_ok_ack, Dl_error_ack

Page 92 highlights

DLPI Primitives Local Management Primitives DL_OK_ACK Acknowledges to the DLS user that a previously issued request primitive was received successfully. It is only initiated for those primitives that require a positive acknowledgment. Format The message consists of one M_PCPROTO message block, which contains the following structure. typedef struct { ulong ulong } dl_ok_ack_t; Parameters dl_primitive dl_primitive; dl_correct_primitve; DL_OK_ACK dl_correct_primitive identifies the successfully received primitive that is being acknowledged. State The message is valid in response to a DL_ATTACH_REQ, DL_DETACH_REQ, DL_UNBIND_REQ, DL_CONNECT_RES, DL_RESET_RES, DL_DISCON_REQ, DL_SUBS_UNBIND_REQ, DL_PROMISCON_REQ, DL_ENABMULTI_REQ, DL_DISADMULTI_REQ, DL_HP_HW_RESET_REQ, DL_HP_RESET_STATS_REQ, or DL_PROMISCOFF_REQ from any of several states as defined in Appendix B, Allowable Sequence of DLPI Primitives, of the DLPI 2.0 specification. New State The resulting state depends on the current state and is defined fully in Appendix B, Allowable Sequence of DLPI Primitives, of the DLPI 2.0 specification. DL_ERROR_ACK Informs the DLS user that the previous request or response was invalid. 92 Chapter 2

  • 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
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

DLPI Primitives
Local Management Primitives
Chapter 2
92
DL_OK_ACK
Acknowledges to the DLS user that a previously issued request primitive
was received successfully. It is only initiated for those primitives that
require a positive acknowledgment.
Format
The message consists of one M_PCPROTO message block, which
contains the following structure.
typedef struct {
ulong
dl_primitive;
ulong
dl_correct_primitve;
} dl_ok_ack_t;
Parameters
dl_primitive
DL_OK_ACK
dl_correct_primitive
identifies the successfully received primitive that is being
acknowledged.
State
The message is valid in response to a DL_ATTACH_REQ,
DL_DETACH_REQ, DL_UNBIND_REQ, DL_CONNECT_RES,
DL_RESET_RES, DL_DISCON_REQ, DL_SUBS_UNBIND_REQ,
DL_PROMISCON_REQ, DL_ENABMULTI_REQ,
DL_DISADMULTI_REQ, DL_HP_HW_RESET_REQ,
DL_HP_RESET_STATS_REQ, or DL_PROMISCOFF_REQ from any of
several states as defined in Appendix B, Allowable Sequence of DLPI
Primitives, of the DLPI 2.0 specification.
New State
The resulting state depends on the current state and is defined fully in
Appendix B, Allowable Sequence of DLPI Primitives, of the DLPI 2.0
specification.
DL_ERROR_ACK
Informs the DLS user that the previous request or response was invalid.