User`s guide

40 DC 900-1343D
DDCMP Programmer’s Guide
2.5 Overview of DDCMP Requests using Raw dlWrite
For DDCMP the dlWrite function supports three dlWrite categories: commands,
report requests, and data transfer, which are discussed in detail in Section 2.5.1 through
Section 2.5.3. Whether you use blocking or non-blocking I/O, each
dlWrite request
must be followed by a
dlRead request to receive the command confirmation, the report
requested, or the acknowledgment of the data transfer. Section 2.6 discusses these dif-
ferent responses received using
dlRead.
In a DDCMP application, the
dlWrite requests must use Raw operation; that is, the
optional arguments structure (page 37) is required to specify protocol-specific infor-
mation.
Table 2–7 shows the DDCMP DLI request codes for different categories of the
dlWrite
function. Each request is explained in the following sections. An unsuccessful dlWrite
request can return one of the following error codes in the dlRead pOptArgs.iICPStatus
field (see Appendix A for error handling):
DLI_ICP_ERR_INBUF_OVERFLOW
Input buffer overflow
DLI_ICP_ERR_OUTBUF_OVERFLOW
Output buffer overflow
Table 2–7: Categories for DDCMP dlWrite Requests
Category
DLI Request Code in the
pOptArgs.usProtCommand Field Usage
Reference
Section
Commands
to ICP
DLI_PROT_CFG_LINK Configure link Section 2.5.1.1
DLI_PROT_CLR_STATISTICS Clear statistics Section 2.5.1.2
DLI_PROT_SEND_BIND Start link Section 2.5.1.3
DLI_PROT_SEND_UNBIND Stop link Section 2.5.1.4
Report Requests
DLI_PROT_GET_BUF_REPORT Request buffer report Section 2.5.2.1
DLI_PROT_GET_STATISTICS_REPORT Request statistics report Section 2.5.2.2
DLI_PROT_GET_STATUS_REPORT Request status report Section 2.5.2.3
Data Transfer DLI_PROT_SEND_NORM_DATA Transmit normal data Section 2.5.3.1