User`s guide

3: FMP DLI Functions

DC 900-1339H 57

3.4.2.6 Request Software Version ID

Use the dlWrite function with the pOptArgs.usProtCommand ﬁeld set to

DLI_PROT_GET_SOFTWARE_VER to request the software version ID. The dlRead software

version report response (the

pOptArgs.usProtCommand ﬁeld is set to

DLI_PROT_GET_SOFTWARE_VER by the DLI) is a one-line report such as the following:

@(#) Simpact FMP for Freeway 2000 – V01.15a 16-May-94 OS/Impact Version V1.5

3.4.3 Data Transfer using Raw dlWrite

FMP provides two write types for sending data: Normal Data and Transparent Data.

The FMP software also provides two command variations (EOM and non-EOM) for

each type of write. These variations are meaningful only when receiving data. When

sending data, they both result in sending a block of data which starts with SOH and

ends with ETX (for BSC and Structured Async lines). This block structure is the most

widely used for BSC type feeds (i.e., feeds from SIAC, OPRA, NASDAQ, etc.). If the

transparent data commands are used, the sent block starts with DLE SOH and ends in

DLE ETX. The FMP software has an ETB Switch option (Section 4.16 on page 92) that

allows sent data blocks to end with ETB instead of ETX in limited situations. More write

format options are available using the Message Blocking option (Section 4.13 on

page 81).

Each

dlWrite consists of a data buffer containing n bytes of data, where n is a number

from 0 to the maximum data size speciﬁed by the Set ICP Message Buffer Size com-

mand (Section 3.4.1.3). The ICP response to each

dlWrite is a data acknowledge which

is also called a local ack (

DLI_PROT_RESP_LOCAL_ACK). The client application program

can process the local acks itself with

dlRead or have the DLI process it automatically (see

below). If an application writes a data message that is larger than the conﬁgured ICP

message buffer size, Freeway returns the data message with the

DLI_ICP_ERR_BUF_TOO_SMALL error code instead of the data acknowledge (local ack)

response.