HP 800 HP DLPI Programmer's Guide - Page 145

Dl_reset_ind

Page 145 highlights

Chapter 2 DLPI Primitives Connection-mode Service Primitives If the disconnect is successful, DL_OK_ACK is sent to the DLS user resulting in state DL_IDLE. If the request fails, DL_ERROR_ACK is returned, and the resulting state is unchanged. Reasons for Failure DL_OUTSTATE The primitive was issued from an invalid state. DL_SYSERR A system error has occurred and the UNIX system error is indicated in the DL_ERROR_ACK. The UNIX error returned may be set to (not limited to) errors listed in Table 2-2 on page 71. DL_RESET_IND Informs the DLS user that either the remote DLS user is re-synchronizing the data link connection, or the DLS provider is reporting loss of data for which it can not recover. The indication conveys the reason for the reset. Format The message consists of one M_PROTO message block containing the structure shown below. typedef struct { ulong dl_primitive; ulong dl_originator; ulong dl_reason; } dl_reset_ind_t; Parameters dl_primitive DL_RESET_REQ dl_originator whether the reset was originated by the DLS user or DLS provider (DL_USER or DL_ PROVIDER, respectively). 145

  • 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
Connection-mode Service Primitives
Chapter 2
145
If the disconnect is successful, DL_OK_ACK is sent to the DLS user
resulting in state DL_IDLE.
If the request fails, DL_ERROR_ACK is returned, and the resulting
state is unchanged.
Reasons for Failure
DL_OUTSTATE
The primitive was issued from an invalid state.
DL_SYSERR
A system error has occurred and the UNIX system error is indicated
in the DL_ERROR_ACK.
The UNIX error returned may be set to (not limited to) errors listed
in Table 2-2 on page 71.
DL_RESET_IND
Informs the DLS user that either the remote DLS user is
re-synchronizing the data link connection, or the DLS provider is
reporting loss of data for which it can not recover. The indication conveys
the reason for the reset.
Format
The message consists of one M_PROTO message block containing the
structure shown below.
typedef struct {
ulong
dl_primitive;
ulong
dl_originator;
ulong
dl_reason;
} dl_reset_ind_t;
Parameters
dl_primitive
DL_RESET_REQ
dl_originator
whether the reset was originated by the DLS user or DLS provider
(DL_USER or DL_ PROVIDER, respectively).