User`s guide

3: Programming Using the DLITE Embedded Interface
DC 900-1516D 41
3.3.2 The Application Program’s Interface to DLITE
Except where described in the previous sections, the embedded DLITE interface does
not change the application’s interface to DLI. While the DLI interface has remained
intact, changes have been made in both the methods supporting DLI and in the under-
lying functionality.
3.3.2.1 Building a DLITE Application
The DLITE API is provided on a static library named LIBVMSEMB.OLB. The user must
include the preprocessor definitions
VMS and DLITE (e.g., /DEFINE=(VMS,DLITE)
when building the application using the Protogate-supplied libraries and header
include files.
3.3.2.2 Blocking and Non-blocking I/O
As described above, DLITE does not support blocking I/O. However, some of the func-
tions are implemented in a blocking manner. The following functions will effectively
block by not returning to the application until all processing is completed for the service
requested:
• dlInit
• dlOpen
• dlClose
• dlTerm
• dlPoll
• dlBufAlloc
• dlBufFree
The following functions are non-blocking. They return to the application immediately
after the operation is queued.
• dlRead