User`s guide

48 DC 900-1516D
ICP2432 User’s Guide for OpenVMS Alpha (DLITE Interface)
5. DLITE adds ICP->iStatus = LittleEndian ? htons (0x4000) : htons (0);
6. DLITE adds ICP->usDataBytes = htons (BufLen + DLI_PROT_HDR_SIZE);
7. If the ICP command is an Attach, or a Write Expedite, the node ID (previously
retrieved from the VMS driver) is stored in
ICP->usParam[0] ( ICP->usParms[0] =
htons( Session->drvNodeID )
).
8.
PROT->usCommand = OptArgs->usProtCommand;
9. PROT->iModifier = OptArgs->iProtModifier;
10. PROT->usLinkID = OptArgs->usProtLinkID;
11. PROT->usCircuitID = OptArgs->usProtCircuitID;
12. PROT->usSessionID = OptArgs->usProtSessionID;
13. PROT->usSequence = OptArgs->usProtSequence;
14. PROT->usXParms[0-1] = OptArgs-> usProtXParms [0-1]);
Non-blocking I/O should expect an EWOULDBLOCK error upon return. A callback is
issued when the write is completed. A callback is invoked for each (both read and write)
write completion.
3.3.2.5 Callbacks
Callbacks represent the completion of an I/O activity; signaling the application to per-
form actions dependent on that I/O completion. In the DLITE interface, this operation
might be a
dlPoll to retrieve session status to ascertain the session’s I/O state, or to
request read/write completes (using
dlPoll).
Callbacks are issued in an AST context. Callbacks are delivered sequentially; they are
never reentered by another callback.