HP 800 HP DLPI Programmer's Guide - Page 156

DL_XID_RES

Page 156 highlights

DLPI Primitives Primitives to Handle XID and TEST Operations length of the DLSAP address of the destination DLS user. If the destination user is implemented using DLPI, this address is the full DLSAP address returned on the DL_BIND_ACK. dl_dest_addr_offset offset from the beginning of the M_PROTO message block where the destination DLSAP address begins. dl_src_addr_length length of the source DLSAP address. If the source user is implemented using DLPI, this address is the full DLSAP address returned on the DL_BIND_ACK. dl_src_addr_offset offset from the beginning of the M_PROTO message block where the source DLSAP address begins. State The message is valid in states DL_IDLE and DL_DATAXFER. New State The resulting state is unchanged. Response The DLS user must respond with a DL_XID_RES. DL_XID_RES Conveys an XID DLSDU from the DLS user to the DLS provider in response to a DL_XID_IND. Format The message consists of one M_PROTO message block, followed by zero or more M_DATA blocks containing zero or more bytes of data. The message structure is as follows: typedef struct { ulong dl_primitive; ulong dl_flag; ulong dl_dest_addr_length; ulong dl_dest_addr_offset; } dl_xid_res_t; 156 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
Primitives to Handle XID and TEST Operations
Chapter 2
156
length of the DLSAP address of the destination DLS user. If the
destination user is implemented using DLPI, this address is the full
DLSAP address returned on the DL_BIND_ACK.
dl_dest_addr_offset
offset from the beginning of the M_PROTO message block where the
destination DLSAP address begins.
dl_src_addr_length
length of the source DLSAP address. If the source user is
implemented using DLPI, this address is the full DLSAP address
returned on the DL_BIND_ACK.
dl_src_addr_offset
offset from the beginning of the M_PROTO message block where the
source DLSAP address begins.
State
The message is valid in states DL_IDLE and DL_DATAXFER.
New State
The resulting state is unchanged.
Response
The DLS user must respond with a DL_XID_RES.
DL_XID_RES
Conveys an XID DLSDU from the DLS user to the DLS provider in
response to a DL_XID_IND.
Format
The message consists of one M_PROTO message block, followed by zero
or more M_DATA blocks containing zero or more bytes of data. The
message structure is as follows:
typedef
struct
{
ulong
dl_primitive;
ulong
dl_flag;
ulong
dl_dest_addr_length;
ulong
dl_dest_addr_offset;
}
dl_xid_res_t;