HP 800 HP DLPI Programmer's Guide - Page 58

DL_HP_PPA_REQ, Format, Parameters, State

Page 58 highlights

DLPI Primitives Local Management Primitives A DLS provider may handle PPA de-initialization using one of the following methods: • Automatic de-initialization upon receipt of the final DL_DETACH_REQ (for style 2 providers), DL_UNBIND_REQ (for style 1 providers), or upon closing of the last stream associated with the PPA • Automatic de-initialization after expiration of a timer following the last DL_DETACH_REQ, DL_UNBIND_REQ, or close as appropriate • No automatic de-initialization; administrative intervention is required to de-initialize the PPA at some point after it is no longer accessed A specific DLS provider may support any of these methods, or possibly combination of them, but the method implemented has no impact on the DLS user. From the DLS user's viewpoint, the PPA is guaranteed to be initialized and available for transmission until it closes or unbinds the stream associated with the PPA. DLS provider specific addendum documentation should describe the method chosen for PPA initialization and de-initialization. DL_HP_PPA_REQ This primitive is used to obtain a list of all the valid PPAs currently installed in the system. This message consists of one M_PCPROTO message block which contains the following structure. Format typedef struct { u_long dl_primitive; } dl_hp_ppa_req_t; Parameters dl_primitive DL_HP_PPA_REQ State 58 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
58
A DLS provider may handle PPA de-initialization using one of the
following methods:
Automatic de-initialization upon receipt of the final
DL_DETACH_REQ (for style 2 providers), DL_UNBIND_REQ (for
style 1 providers), or upon closing of the last stream associated with
the PPA
Automatic de-initialization after expiration of a timer following the
last DL_DETACH_REQ, DL_UNBIND_REQ, or close as appropriate
No automatic de-initialization; administrative intervention is
required to de-initialize the PPA at some point after it is no longer
accessed
A specific DLS provider may support any of these methods, or possibly
combination of them, but the method implemented has no impact on the
DLS user. From the DLS user
s viewpoint, the PPA is guaranteed to be
initialized and available for transmission until it closes or unbinds the
stream associated with the PPA.
DLS provider specific addendum documentation should describe the
method chosen for PPA initialization and de-initialization.
DL_HP_PPA_REQ
This primitive is used to obtain a list of all the valid PPAs currently
installed in the system.
This message consists of one M_PCPROTO message block which
contains the following structure.
Format
typedef struct {
u_long
dl_primitive;
} dl_hp_ppa_req_t;
Parameters
dl_primitive
DL_HP_PPA_REQ
State