User`s guide

2: DDCMP DLI Functions
DC 900-1343D 31
For an embedded ICP using the DLITE interface, Figure 2–2 shows the “main” section
and two DDCMP sessions. You need to include only those parameters whose values dif-
fer from the defaults. The DLITE interface supports only Raw operation. For more
information on the DLITE interface, refer to the user’s guide for your embedded ICP
and operating system (for example, the ICP2432 User’s Guide for Windows NT).
main // DLI “main” section: //
{
asyncIO = “yes”; // Use non-blocking I/O //
tsiCfgName = "." // Location of NT log/trace svc //
// (tsiCfgName unused for VMS) //
// The following two parameters are for DLITE only: //
maxBuffers = 1024;
maxBufSize = 1200;
}
ICP0link0 // First session name: //
{ // Client-related parameters: //
alwaysQIO = “yes”; // Queue I/Os even if complete //
asyncIO = “yes”; // Use non-blocking I/O //
cfgLink = “no”; // Client configures links //
enable = “no”; // Client enables links //
localAck = “no”; // Client processes transmit ack//
boardNo = 0; // First ICP is zero //
portNo = 0; // First ICP link is zero //
protocol = “raw”; // DLITE requires Raw operation //
maxBufSize = 1200; // Used by DLITE //
}
ICP0link1 // Second session name: //
{ // Client-related parameters: //
alwaysQIO = “yes”; // Queue I/Os even if complete //
asyncIO = “yes”; // Use non-blocking I/O //
cfgLink = “no”; // Client configures links //
enable = “no”; // Client enables links //
localAck = “no”; // Client processes transmit ack//
boardNo = 0; // First ICP is zero //
portNo = 1; // First ICP link is zero //
protocol = “raw”; // DLITE requires Raw operation //
maxBufSize = 1200; // Used by DLITE //
}
Figure 2–2: DLI Configuration File for Two Embedded ICP Links (DLITE Interface)
2/16/99 Per
Vic
Dobrawa:
To avoid
potential
confusion,
deleted
“transport”
parameter
(not used).