User`s guide

3: Programming Using the DLITE Embedded Interface
DC 900-1516D 49
There is no difference between the “main” callback and the “session” callback. They are
initiated sequentially by DLITE. For sake of efficiency, Protogate recommends the user
make use of only one.
To maintain conformity with the existing DLI, callbacks are delivered upon completion
of
dlOpen processing. Although dlOpen processing does not generate a callback from the
system (i.e., an AST is not “kicked-off”) the API does, just prior to exiting the
dlOpen
processing, emulate the event by placing a “callback” request in an internal callback
queue for delivery to the application.
In a similar manner, callbacks on
dlClose requests are generated and delivered by the
API.
3.3.2.6 DLITE Error Codes
The error codes listed in Ta bl e 3 –1 have been added to DLITE.
Selected VMS system errors are mapped into existing DLI error codes (
dlerrno) so the
application can recognize the error condition and react accordingly. VMS errors are
mapped to
dlerrno as described in Ta bl e 3–2.
3.3.3 Configuration Files
DLITE uses only the DLI configuration files (TSI configuration files are not used and
are not required). The DLI configuration file must specify “
protocol = raw” in the session
sections. With this specification, no parameters are allowed in the protocol section.
The DLI configuration file has been changed to include parameters previously specified
in the TSI configuration file (which is no longer used). These parameters are required
to maintain conformity with those applications porting from DLI to DLITE. This file
has been changed as follows:
MaxBuffers — This parameter has been added to the “main” section. It replaces the
MaxBuffers parameter previously defined in the TSI configuration file. This value