User`s guide

166 DC 900-1317J
ADCCP NRM Programmer’s Guide
D.31 buffer-rpt-ack-packet
Packet Description
This packet is received in response to a "buffer-rpt-packet".
Packet Header
Freeway (DLI api only):
usFWPacketType = FW_DATA
usFWCommand = FW_ICP_READ
usFWStatus = 0
ICP:
usICPClientID = 0
usICPServerID = 0
[usLength = length of data + 16 (used for non DLI api only)]
usICPCommand = DLI_ICP_CMD_READ
iICPStatus = - 0 or DLI return status
usICPParams[0] = icpNode
usICPParams[1] = dliSessionID
usICPParams[2] = 0
Protocol:
usProtCommand = DLI_PROT_RESP_BUF_REPORT
iProtModifier = 0
usProtLinkID = port number
usProtCircuitID = 0
usProtSessionID = icpSessionID
usProtSequence = userMarker (user-chosen marker)
usProtXparms[0] = stationID (or zero)
usProtXparms[1] = 68 (or 84) (data field size)
Note
The Freeway header is used only with DLI (it is not applicable for
DLITE), and the
usLength field of the ICP header is used only with-
out DLI.
Data
The data area in the DLI_PROT_RESP_BUF_REPORT packet contains a set of 32-bit integer
values organized in the form of the
SDLC_BUFFER_REPORT structure type shown in
Figure D–1 together with its component substructure definitions.
Note
If your client machine does not implement a 32-bit memory archi-
tecture, or if your compiler does not define “int” as a 32-bit data
type, you might need to modify the
sdlc_buffer_report structure
definition for your computing environment.