User`s guide

5: BSC 2780/3780 DLI Functions
DC 900-1340I 147
If the DLI localAck configuration parameter is set to “yes” (which is the default), the
data acknowledge response is implied by a successful
dlWrite.
An unsuccessful dlWrite data transfer request can return one of the following error
codes in the
dlRead pOptArgs.iICPStatus field (see Appendix D for error handling):
DLI_ICP_ERR_LINK_INACTIVE
The link is stopped.
DLI_ICP_ERR_BAD_MODE
The function request is not available for the requested
access mode.
DLI_ICP_ERR_XMIT_TIMEOUT
The protocol software was unable to transmit the data.
This error occurs when some or all of the modem sig-
nals are not present.
5.4.3.1 Send Normal Data
If your application needs to perform a Raw dlWrite, use the dlWrite function with the
pOptArgs.usProtCommand field set to DLI_PROT_SEND_NORM_DATA or
DLI_PROT_SEND_NORM_DATA_EOM to send normal data. Refer back to Section 2.3 on
page 38 for examples of normal data.
As an example, assuming the ICP message buffer size is 2048 bytes, to send a 4096-byte
normal data block would require two writes, setting the pOptArgs.usProtCommand field
to
DLI_PROT_SEND_NORM_DATA and DLI_PROT_SEND_NORM_DATA_EOM, respectively. A 2048-
byte message (or less) would require one write transfer setting the
pOptArgs.usProtCommand field to DLI_PROT_SEND_NORM_DATA_EOM.
To automatically send normal data with EOM, set writeType = “normal” in the DLI con-
figuration file (Table 7–2 on page 191).
5.4.3.2 Send Transparent Data
If your application needs to perform a Raw dlWrite, use the dlWrite function with the
pOptArgs.usProtCommand field set to DLI_PROT_SEND_TRANS_DATA or