HP 800 HP DLPI Programmer's Guide - Page 107

Dl_badaddr, Dl_baddata

Page 107 highlights

Chapter 2 DLPI Primitives Connectionless-mode Service Primitives offset from the beginning of the M_PROTO message block where the destination DLSAP address begins. dl_priority priority value within the supported range for this particular DLSDU. This value must be set to 0 (zero). State The message is valid in state DL_IDLE. New State The resulting state is unchanged. Response If the DLS provider accepts the data for transmission, there is no response. This does not, however, guarantee that the data will be delivered to the destination DLS user, since the connectionless data transfer is not a confirmed service. If the request is erroneous, DL_UDERROR_IND is returned, and the resulting state is unchanged. If for some reason the request cannot be processed, the DLS provider may generate a DL_UDERROR_IND to report the problem. There is, however, no guarantee that such an error report will be generated for all undeliverable data units, since connectionless data transfer is not a confirmed service. Reasons for Failure DL_BADADDR The destination DLSAP address was in an incorrect format or contained invalid information. DL_BADDATA The amount of data in the current DLSDU exceeded the DLS provider's DLSDU limit. DL_OUTSTATE Primitive was issued from an invalid state. DL_UNSUPPORTED Requested priority not supplied by provider. 107

  • 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
Connectionless-mode Service Primitives
Chapter 2
107
offset from the beginning of the M_PROTO message block where the
destination DLSAP address begins.
dl_priority
priority value within the supported range for this particular DLSDU.
This value must be set to 0 (zero).
State
The message is valid in state DL_IDLE.
New State
The resulting state is unchanged.
Response
If the DLS provider accepts the data for transmission, there is no
response. This does not, however, guarantee that the data will be
delivered to the destination DLS user, since the connectionless data
transfer is not a confirmed service.
If the request is erroneous, DL_UDERROR_IND is returned, and the
resulting state is unchanged.
If for some reason the request cannot be processed, the DLS provider
may generate a DL_UDERROR_IND to report the problem. There is,
however, no guarantee that such an error report will be generated for all
undeliverable data units, since connectionless data transfer is not a
confirmed service.
Reasons for Failure
DL_BADADDR
The destination DLSAP address was in an incorrect format or
contained invalid information.
DL_BADDATA
The amount of data in the current DLSDU exceeded the DLS
provider's DLSDU limit.
DL_OUTSTATE
Primitive was issued from an invalid state.
DL_UNSUPPORTED
Requested priority not supplied by provider.