FMP Programmer’s Guide DC 900-1339H Simpact, Inc.
Simpact, Inc. 9210 Sky Park Court San Diego, CA 92123 (619) 565-1865 FMP Programmer’s Guide © 1994 through 1998 Simpact, Inc. All rights reserved Printed in the United States of America This document can change without notice. Simpact, Inc. accepts no liability for any errors this document might contain. Freeway is a registered trademark of Simpact, Inc. All other trademarks and trade names are the properties of their respective holders.
Contents List of Figures 7 List of Tables 9 Preface 11 1 17 Introduction 1.1 Product Overview . . . . . . . . . . . . . . . . . . . 1.1.1 Freeway Server . . . . . . . . . . . . . . . . . . 1.1.2 Embedded ICP . . . . . . . . . . . . . . . . . . 1.2 Freeway Client-Server Environment . . . . . . . . . 1.2.1 Establishing Freeway Server Internet Addresses 1.3 Embedded ICP Environment . . . . . . . . . . . . . 1.4 Client Operations . . . . . . . . . . . . . . . . . . . 1.4.
FMP Programmer’s Guide 2.1.2 Asynchronous Market Feeds . . . . . . . 2.1.2.1 Structured Asynchronous Frame . 2.1.2.2 Unstructured Asynchronous Frame 2.1.3 Isochronous Market Feeds . . . . . . . . 2.1.4 Bonneville Market Feed. . . . . . . . . . 2.1.5 Character Codes. . . . . . . . . . . . . . 2.1.6 Message Transmission . . . . . . . . . . 2.2 FMP Access Modes . . . . . . . . . . . . . . . 3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3.5 4 Overview of FMP Responses using Raw dlRead . . . . . . . 3.5.1 Received Data . . . . . . . . . . . . . . . . . . . . . . . 3.5.2 Error, Confirmation, and Acknowledgment Responses. 3.5.3 Reports in Response to dlWrite Information Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . FMP Link Configuration Options 4.1 4.2 Data Rate Option (1) . . . . . . . . . . . . . . . Clock Source Option (2) . . . . . . . . . . . . . 4.2.1 External . . . . . . . . . . . . . . . . .
FMP Programmer’s Guide 4.13.6 Message Blocking for the Bonneville Feed . . . . . . 4.14 Block Checking Option (20). . . . . . . . . . . . . . . . 4.15 Queue Limit Option (21) . . . . . . . . . . . . . . . . . 4.16 ETB Switch Option (24) . . . . . . . . . . . . . . . . . . 4.17 DSR Delay Option (30) . . . . . . . . . . . . . . . . . . 4.18 Line Mode Option (33) . . . . . . . . . . . . . . . . . . 4.19 Asynchronous Terminating Character Option (34) . . . 4.20 Number of Terminating Characters Option (38). . .
List of Figures Figure 1–1: Freeway Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 18 Figure 1–2: Embedded ICP Configuration . . . . . . . . . . . . . . . . . . . . . . . 19 Figure 1–3: A Typical Freeway Server Environment . . . . . . . . . . . . . . . . . . 21 Figure 3–1: “C” Definition of DLI Optional Arguments Structure . . . . . . . . . . 44 Figure 3–2: Link Configuration Block with Two Options . . . . . . . . . . . . . . .
FMP Programmer’s Guide 8 DC 900-1339H
List of Tables Table 2–1: Messages Duplicated for all Non-Control Sessions on a Link . . . . . . . 33 Table 2–2: FMP Session Access Modes . . . . . . . . . . . . . . . . . . . . . . . . . 33 Table 2–3: FMP Access Modes for Various Operations . . . . . . . . . . . . . . . . . 34 Table 3–1: DLI Call Sequence for FMP (Blocking I/O). . . . . . . . . . . . . . . . . 40 Table 3–2: DLI Call Sequence for FMP (Non-blocking I/O) . . . . . . . . . . . . . .
FMP Programmer’s Guide 10 DC 900-1339H
Preface Purpose of Document This document describes the operation and programming interface required to use Simpact’s Financial Market Protocols (FMP) product for Simpact’s Freeway communications server or embedded ICP. It is written for subscribers who receive broadcast market feeds from various stock exchanges. Note In this document, the term “Freeway” can mean either a Freeway server or an embedded ICP.
FMP Programmer’s Guide • a Freeway communications server or embedded ICP that runs the communications software • a client computer that runs the following: • TCP/IP (for a Freeway server) • Freeway DLI • the user application program Organization of Document Chapter 1 is an overview of Freeway and the FMP product. Chapter 2 summarizes the basic communication protocol formats available on the FMP software package.
Preface General Product Overviews • • • • Freeway 1100 Technical Overview Freeway 2000/4000/8800 Technical Overview ICP2432 Technical Overview ICP6000X Technical Overview 25-000-0419 25-000-0374 25-000-0420 25-000-0522 Hardware Support • • • • • • • • • • Freeway 1100/1150 Hardware Installation Guide Freeway 1200 Hardware Installation Guide Freeway 1300 Hardware Installation Guide Freeway 2000/4000 Hardware Installation Guide Freeway 8800 Hardware Installation Guide Freeway ICP6000R/ICP6000X Hardware
FMP Programmer’s Guide Application Program Interface (API) Programming Support • • • Freeway Data Link Interface Reference Guide Freeway Transport Subsystem Interface Reference Guide QIO/SQIO API Reference Guide DC 900-1385 DC 900-1386 DC 900-1355 Socket Interface Programming Support • Freeway Client-Server Interface Control Document DC 900-1303 Toolkit Programming Support • Freeway Server-Resident Application and Server Toolkit Programmer’s Guide OS/Impact Programmer’s Guide Protocol Software To
Preface Document Conventions This document follows the most significant byte first (MSB) and most significant word first (MSW) conventions for bit-numbering and byte-ordering. In all packet transfers between the client applications and the ICPs, the ordering of the byte stream is preserved. However, FMP packed data contains word values that are not byte-swapped.
FMP Programmer’s Guide Document Revision DC 900-1339F Release Date April 1997 Description • • • • • DC 900-1339G August 1997 DC 900-1339H June 1998 • • • • • • • • • • Add Simpact browser configuration information Add normal and transparent data codes to dlRead responses (Table 3–8 on page 61) Modify Table 2–1 on page 33, Section 3.4.3 on page 57, Section 3.5.1 on page 60, Table 5–1 on page 104, and Table C–1 on page 118 Add Data Packing option (Section 4.
Chapter 1 Introduction 1.1 Product Overview Most recent modification date: 03/25/98 Leslie: Remove “Freeway Embedded” and just say “embedded ICP” (as an interim fix prior to BIG makeover). Simpact provides a variety of wide-area network (WAN) connectivity solutions for real-time financial, defense, telecommunications, and process-control applications. Simpact’s Freeway server offers flexibility and ease of programming using a variety of LAN-based server hardware platforms.
FMP Programmer’s Guide To maintain high data throughput, Freeway uses a multi-processor architecture to support the LAN and WAN services. The LAN interface is managed by a single-board computer, called the server processor. It uses the commercially available VxWorks operating system to provide a full-featured base for the LAN interface and layered services needed by Freeway. Freeway can be configured with multiple WAN interface processor boards, each of which is a Simpact ICP.
1: Introduction 1.1.2 Embedded ICP The embedded ICP connects your client computer directly to the WAN (for example, using Simpact’s ICP2432 PCIbus board). The embedded ICP provides client applications with the same WAN connectivity as the Freeway server, using the same data link interface. The ICP runs the communication protocol software using Simpact’s real-time operating system. Figure 1–2 shows the embedded ICP configuration.
FMP Programmer’s Guide Summary of product features: • Provision of WAN connectivity either through a LAN-based Freeway server or directly using an embedded ICP • Elimination of difficult LAN and WAN programming and systems integration by providing a powerful and consistent data link interface • Variety of off-the-shelf communication protocols available from Simpact which are independent of the client operating system and hardware platform • Support for multiple WAN communication protocols simultane
1: Introduction 1.2 Freeway Client-Server Environment The Freeway server acts as a gateway that connects a client on a local-area network to a wide-area network. Through Freeway, a client application can exchange data with a remote data link application. Your client application must interact with the Freeway server and its resident ICPs before exchanging data with the remote data link application.
FMP Programmer’s Guide 1.2.1 Establishing Freeway Server Internet Addresses The Freeway server must be addressable in order for a client application to communicate with it. In the Figure 1–3 example, the TCP/IP Freeway server name is freeway2, and its unique Internet address is 192.52.107.100. The client machine where the client application resides is client1, and its unique Internet address is 192.52.107.99.
1: Introduction 1.4.2 Opening a Session After the DLI and TSI configurations are properly defined, your client application uses the dlOpen function to establish a DLI session with an ICP link. As part of the session establishment process, the DLI establishes a TSI connection with the Freeway MsgMux through the TCP/IP BSD-style socket interface for the Freeway server, or directly to the client driver for the embedded ICP environment. 1.4.
FMP Programmer’s Guide Each serial link on the FMP ICP can be configured as a receiver of one of several defined market feeds. Each link operates independently of the other links on the same ICP and can be configured with different communication options. Data messages on the primary market feeds are broadcast using bisynchronous, asynchronous, or isochronous frames.
1: Introduction exchanged between the client application and Freeway; refer to the Freeway Data Link Interface Reference Guide. 1.5.
FMP Programmer’s Guide 26 DC 900-1339H
Chapter 2 FMP Protocol Summary 2.1 Message Formats Although the text message format of each primary market feed is unique, the protocols used to frame the text fall into three general categories: bisynchronous, asynchronous, and isochronous. This chapter describes these three protocol categories. Information regarding the protocol framing of your feed can be found in the digital feed specification document supplied by the stock exchange or feed provider.
FMP Programmer’s Guide 2.1.1 Bisynchronous Market Feeds Most of the U.S. primary feeds use the bisynchronous (BSC) method of transmission to broadcast data. BSC market feeds require the presence of a clock signal to receive the feed. Clock signals are usually supplied externally by the synchronous modem. FMP receives BSC-type framing when the line mode option is set to bisynchronous. 2.1.1.
2: FMP Protocol Summary an end-of-text (ETX) character. Each text block is followed by a block check character (BCC) that is a redundancy check (CRC-16 or LRC-8) of the characters in the entire block starting with the first character following SOH or STX and ending with the ETX character. The number of SYN characters are described in Section 4.3 on page 70. PAD characters ensure complete transmission of the data block.
FMP Programmer’s Guide of frames when the line mode option is set to one of the asynchronous settings (see Chapter 4 for more information on these option settings). 2.1.2.1 Structured Asynchronous Frame A structured asynchronous frame is similar to a BSC frame containing one message. The diagram below shows the structured asynchronous text frame which is identical to a normal BSC 3780 frame without leading SYN or trailing PAD characters.
2: FMP Protocol Summary An example of an unstructured asynchronous feed is SIAC’s Ticker A feed. 2.1.3 Isochronous Market Feeds The isochronous protocol is asynchronous character framing that is clocked by an external source (such as a modem). FMP receives these feeds in the same manner as the unstructured asynchronous feeds except that the line mode option must be set to isochronous and the clock source option must be set to external. See the diagram in Section 2.1.2.2. 2.1.
FMP Programmer’s Guide gram and the Freeway server or embedded ICP is always in ASCII and is translated by the FMP software as required. 2.1.6 Message Transmission In addition to receiving the market feeds, the FMP product can transmit data in the same format. This capability is not usually used during normal operations; however, it can be used for port-to-port loopback testing. The client sends data to the FMP software as a complete message. A message consists of one buffer of text data.
2: FMP Protocol Summary Table 2–1: Messages Duplicated for all Non-Control Sessions on a Link Response Codes DLI_PROT_RECV_PACKED_DATA Usage Received packed data Reference Section Section 3.5.1 on page 60 DLI_PROT_RECV_PACKED_DATA_EOM Received packed data (EOM) Section 3.5.1 on page 60 DLI_PROT_RESP_ERROR Error reports Section 3.5.2 on page 63 DLI_PROT_SEND_NORM_DATA Received normal data Section 3.5.1 on page 60 DLI_PROT_SEND_NORM_DATA_EOM Received normal data (EOM) Section 3.5.
FMP Programmer’s Guide Table 2–3: FMP Access Modes for Various Operations Operation 34 Access Mode Required Reference Section Set Translation Table Manager or Shared Manager Section 3.4.1.1 Clear Statistics Manager or Shared Manager Section 3.4.1.2 Change Buffer Size Any mode Section 3.4.1.3 Configure Link Manager or Shared Manager Section 3.4.1.4 Start Link Manager or Shared Manager Section 3.4.1.5 Stop Link Manager or Shared Manager Section 3.4.1.
Chapter 3 Note FMP DLI Functions In this document, the term “Freeway” can mean either a Freeway server or an embedded ICP. For the embedded ICP, also refer to the user’s guide for your ICP and operating system (for example, the ICP2432 User’s Guide for Windows NT). This chapter describes how to use the data link interface (DLI) functions to write client applications interfacing to the Freeway FMP protocol software.
FMP Programmer’s Guide 3.1 Summary of DLI Concepts The DLI presents a consistent, high-level, common interface across multiple clients, operating systems, and transport services. It implements functions that permit your application to use data link services to access, configure, establish and terminate sessions, and transfer data across multiple data link protocols. The DLI concepts are described in detail in the Freeway Data Link Interface Reference Guide. This section summarizes the basic information.
3: FMP DLI Functions • You can specify ICP link parameters in the DLI ASCII configuration file and then run the dlicfg preprocessor program (see Chapter 5). The dlOpen function uses the resulting DLI binary configuration file to perform the link configuration during the DLI session establishment process. • You can perform ICP link configuration within the client application (described in Section 3.4.1.4). This method is useful if you need to change link configuration without exiting the application. 3.
FMP Programmer’s Guide Note For most applications, the FMP protocol requires Raw read and write requests to specify protocol-specific information. 3.1.3 Blocking versus Non-blocking I/O Note Earlier Freeway releases used the term “synchronous” for blocking I/O and “asynchronous” for non-blocking I/O. Some parameter names reflect the previous terminology.
3: FMP DLI Functions 3.1.4 Buffer Management Currently the interrelated Freeway, DLI, TSI and ICP buffers default to a size of 1024 bytes. Caution DC 900-1339H If you need to change a buffer size for your application, refer to the Freeway Data Link Interface Reference Guide for explanations of the complexities that you must consider.
FMP Programmer’s Guide 3.2 Example FMP Call Sequences Table 3–1 shows the sequence of DLI function calls to send and receive data using blocking I/O. Table 3–2 is the non-blocking I/O example. The remainder of this chapter and the Freeway Data Link Interface Reference Guide give further information about each function call. Section 3.1.3 on page 38 describes blocking and non-blocking I/O.
3: FMP DLI Functions Note When using non-blocking I/O, a dlRead request must always be queued to avoid loss of data or responses from the ICP (see Step 5 of Table 3–2). Table 3–2: DLI Call Sequence for FMP (Non-blocking I/O) 1. Call dlInit to initialize the DLI operating environment. The first parameter is your DLI binary configuration file name. 2. Call dlOpen for each required session (link) to get a session ID. 3. Call dlPoll to confirm the success of each session ID obtained in Step 2. 4.
FMP Programmer’s Guide 3.3 Overview of DLI Functions for FMP This section summarizes the DLI functions used in writing a client application.
3: FMP DLI Functions Table 3–3: DLI Functions: Syntax and Parameters (Listed in Typical Call Order) DLI Function int dlInit Parameter(s) (char *cfgFile, char *pUsrCb, int (*fUsrIOCH)(char *pUsrCb)); int dlOpena (char *cSessionName, int (*fUsrIOCH) (char *pUsrCB, int iSessionID)); int dlPoll (int iSessionID, int iPollType, char **ppBuf, int *piBufLen, char *pStat, DLI_OPT_ARGS **ppOptArgs); int dlpErrString (int dlErrNo); Parameter Usage DLI binary configuration file name Optional I/O complete control bl
FMP Programmer’s Guide 3.3.1 DLI Optional Arguments Section 3.4 and Section 3.5 describe the dlWrite and dlRead functions for an FMP application. Both functions can use the optional arguments parameter to provide the protocol-specific information required for Raw operation (Section 3.1.2). The “C” definition of the optional arguments structure is shown in Figure 3–1.
3: FMP DLI Functions 3.4 Overview of FMP Requests using dlWrite For FMP the dlWrite function supports three dlWrite categories: commands, information requests, and data transfer, which are discussed in detail in Section 3.4.1 through Section 3.4.3. Whether you use blocking or non-blocking I/O, each dlWrite request must be followed by a dlRead request to receive the command confirmation, information requested, or acknowledgment of the data transfer. Section 3.
FMP Programmer’s Guide DLI_ICP_ERR_INBUF_OVERFLOW Input buffer overflow DLI_ICP_ERR_OUTBUF_OVERFLOW Output buffer overflow Table 3–4: Categories for FMP dlWrite Requests Category Commands to ICP Report Requests Data Transfer a 46 DLI Request Code Usage DLI_PROT_CFG_LINK Configure link DLI_PROT_CLR_STATISTICS Clear statistics DLI_PROT_SEND_BIND Start link DLI_PROT_SEND_UNBIND Stop link DLI_PROT_SET_BUF_SIZE Set ICP message buffer size DLI_PROT_SET_TRANS_TABLE Set translation table DLI
3: FMP DLI Functions 3.4.1 Commands using Raw dlWrite Section 3.4.1.1 through Section 3.4.1.6 explain how to issue specific commands to the FMP software using the dlWrite function. Call dlRead to receive the command confirmation response (the dlRead pOptArgs.usProtCommand field is set by the DLI). 3.4.1.1 Set Translation Table Command Use the dlWrite function with the pOptArgs.usProtCommand field set to DLI_PROT_SET_TRANS_TABLE to set translation table 1 or 2 (translation table 3 cannot be changed).
FMP Programmer’s Guide An unsuccessful Clear Statistics command can return the following error code in the dlRead pOptArgs.iICPStatus field (see Appendix C for error handling): DLI_ICP_ERR_BAD_MODE The function request is not available for the requested access mode; see Table 2–2 on page 33. 3.4.1.3 Set ICP Message Buffer Size Command The ICP message buffer size applies to all links on the ICP. The DLI sets the ICP message buffer size as part of the configuration process during the dlOpen command.
3: FMP DLI Functions DLI_ICP_ERR_BAD_MODE The function request is not available for the requested access mode; see Table 2–2 on page 33. DLI_ICP_ERR_BAD_PARMS The parameter value(s) used for the function call are illegal. DLI_ICP_ERR_LINK_ACTIVE The link is already started. 3.4.1.
FMP Programmer’s Guide pBuf configuration option = 1 (data rate) Word 0 configuration value = 9 (9600) 1 configuration option = 20 (block checking) 2 configuration value = 0 (disabled) 3 0 4 iBufLen = 10 Figure 3–2: Link Configuration Block with Two Options Interface option (Section 4.22 on page 95) is valid only on the Freeway 1000, not the Freeway 2000 or 4000. An unsuccessful Configure Link command can return one of the following error codes in the dlRead pOptArgs.
3: FMP DLI Functions link to transmit and receive data according to the current configuration settings. After a link starts, data transmission can begin on the line. For blocking I/O, a successful Start Link command returns zero, but you must call dlRead to receive the DLI_PROT_RESP_BIND_ACK response indicating that the FMP soft- ware has received a data set ready (DSR) signal from the remote end.
FMP Programmer’s Guide figure the link using the Link Configuration command). The link is restarted again by issuing a Start Link command. For blocking I/O a successful Stop Link command returns zero, but you must call dlRead to receive the DLI_PROT_RESP_UNBIND_ACK response indicating the link is deacti- vated. If you are using non-blocking I/O, you must also make a dlRead request to read the completion status.
3: FMP DLI Functions 3.4.2 Information Requests using Raw dlWrite Section 3.4.2.1 through Section 3.4.2.6 explain how to issue specific information requests to the FMP software using the dlWrite function. You must then make a Raw dlRead request to receive the report information (the dlRead pOptArgs.usProtCommand field is set by the DLI to reflect the type of report, and the iBufLen parameter indicates the size of the message).
FMP Programmer’s Guide 3.4.2.2 Request Configuration Report Use the dlWrite function with the pOptArgs.usProtCommand field set to DLI_PROT_GET_LINK_CFG to request the current configuration option settings for a link. The dlRead configuration report response (the pOptArgs.usProtCommand field is set to DLI_PROT_GET_LINK_CFG by the DLI) consists of a sequence of 16-bit word pairs con- taining the option number in the first word and the option setting in the second.
3: FMP DLI Functions 3.4.2.4 Request Status Report Use the dlWrite function with the pOptArgs.usProtCommand field set to DLI_PROT_GET_STATUS_REPORT to request the current link status. The status report returned by dlRead is a snapshot of the link’s hardware and software condition. The dlRead status report response (the pOptArgs.usProtCommand field is set to DLI_PROT_GET_STATUS_REPORT by the DLI) is an eleven-word report containing the cur- rent link status as shown in Table 3–7.
FMP Programmer’s Guide Link status indicates whether the link is on, off, or starting. Starting indicates that a connection command was received, but the link did not start because it did not receive the data set ready (DSR) signal from the remote station. A line is off until it is started and the DSR signal has been received from the remote station. Current operation mode settings indicate whether the line can operate. A line is idle when data transmission or reception can occur.
3: FMP DLI Functions 3.4.2.6 Request Software Version ID Use the dlWrite function with the pOptArgs.usProtCommand field set to DLI_PROT_GET_SOFTWARE_VER to request the software version ID. The dlRead software version report response (the pOptArgs.usProtCommand field 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.
FMP Programmer’s Guide If the localAck DLI configuration parameter is set to “no” (see the Freeway Data Link Interface Reference Guide), the client application must make a dlRead request to receive the data acknowledge response for each dlWrite data transfer request (the dlRead pOptArgs.usProtCommand field is set to DLI_PROT_RESP_LOCAL_ACK by the DLI). One DLI_PROT_RESP_LOCAL_ACK response (with the dlRead pOptArgs.
3: FMP DLI Functions To automatically send normal data with EOM, set writeType = “normal” in the DLI configuration file (Table 5–1 on page 104). 3.4.3.2 Send Transparent Data If your application needs to perform a Raw dlWrite, use the dlWrite function with the pOptArgs.usProtCommand field set to DLI_PROT_SEND_TRANS_DATA or DLI_PROT_SEND_TRANS_DATA_EOM to send transparent data. The client can send transpar- ent data in either ASCII or EBCDIC mode. In either mode, the data is not code-converted.
FMP Programmer’s Guide 3.5 Overview of FMP Responses using Raw dlRead Table 3–8 shows the valid FMP codes sent to your application in response to a Raw dlRead request; the returned dlRead pOptArgs.usProtCommand field indicates the response code. If the dlRead return value is zero or positive, it indicates the number of bytes read; if it is less than zero, an error has occurred. FMP error codes that can be associated with the responses are described in Appendix C.
3: FMP DLI Functions Table 3–8: FMP Response Codes Category Received Data DLI Response Code in pOptArgs.usProtCommand Field Normal or transparent data with header DLI_PROT_RECV_PACKED_DATA_EOM Normal or transparent data with header (end of message) DLI_PROT_SEND_NORM_DATA Normal data DLI_PROT_SEND_NORM_DATA_EOM Normal data (EOM) DLI_PROT_SEND_TRANS_DATA Transparent data DLI_PROT_SEND_TRANS_DATA_EOM Transparent data (EOM) DLI_PROT_RESP_ERROR Error report; the dlRead pOptArgs.
FMP Programmer’s Guide the most widely used format for BSC type feeds (i.e., feeds from SIAC, OPRA, NASDAQ, etc.). When a data block ending with ETB is received or if the ICP must split a single block in order to fit the records into a smaller message buffer, the ICP uses the nonEOM variation. For most data feed applications, both variations should be treated as the same. If the Message Blocking option (Section 4.
3: FMP DLI Functions Caution The 16-bit header fields are not byte-swapped by the FMP software. The client application must perform any necessary swapping. Additionally, packed data headers might not start on word boundaries. The packed data is in most significant byte (MSB) first order in the data area. 3.5.2 Error, Confirmation, and Acknowledgment Responses Table 3–8 lists the possible FMP error, confirmation, and acknowledgment response codes returned in the dlRead pOptArgs.usProtCommand field.
FMP Programmer’s Guide 64 DC 900-1339H
Chapter 4 FMP Link Configuration Options This chapter describes the various link configuration options that can be defined using the DLI configuration file described in Section 5.2 on page 102. Alternatively, the link options can be set using the dlWrite Configure Link command as described in Section 3.4.1.4 on page 49. Table 4–1 lists all the available options in numerical order along with the allowed settings and defaults.
FMP Programmer’s Guide Table 4–1: FMP Default Options and Settings Option Data Rate Value 1 0 75 bits/second 1 110 2 135 3 150 4 300 5 600 6 1200 7 2400 8 4800 9 Clock Source Default (✓) Number 2 ✓ Setting 9600 10 19200 11 38400 12 56000 0 ✓ 1 External Internal Number of Leading Sync Characters 4 n 3 n = sync chars (2 ≤ n ≤ 8) Protocol 5 2 2 FMP Parity 6 0 1 None ✓ 2 Character Set Transmission Block Size 66 7 8 0 Odd Even ✓ ASCII/LRC-8 1 EBCDI
4: FMP Link Configuration Options Table 4–1: FMP Default Options and Settings (Cont’d) Option Data Translation Number Value 10 0 1 Data Packing 12 Default (✓) Setting Disable ✓ Table 1 (default is EBCDIC) 2 Table 2 (default is Baudot level 6) 3 Table 3 (default is Baudot level 5) 0 Disable 1 ✓ Enable 0 n = delay in tenths of seconds (0 ≤ n ≤ 8000) Buffer Timer 15 n Modem Control 16 0 1 HDX-1 ✓ FDX-1 2 HDX-2 3 FDX-2 4 HDX-3 5 FDX-3 6 HDX-4 7 FDX-4 Feed ID 18 n 0
FMP Programmer’s Guide Table 4–1: FMP Default Options and Settings (Cont’d) Option Line Mode Number Value Default (✓) 33 0 ✓ Structured Asynchronous 2 8-bit Unstructured Asynchronous 3 7-bit Unstructured Asynchronous 4 6-bit Unstructured Asynchronous 5 5-bit Unstructured Asynchronous 6 8-bit Isochronous 7 Bonneville Asynchronous Feed 34 A Number of Terminating Characters 38 0 39 3 40 A = ASCII character code (0–255) No terminating character 1 ✓ One terminating character (as
4: FMP Link Configuration Options Therefore, if FMP is being used to transmit data, the data rate should be set to match, or be slower than, the modem clock rate. The data rate on a link can be set from 75 through 56,000 bits/second. When using data rates above 19,200 bits/second, be careful not to overload the communications server processor.
FMP Programmer’s Guide 4.2.2 Internal When the internal clock setting is used, the clock signal is generated at the rate specified in the data rate option (Section 4.1). The generated clock signal is used for transmit clocking and is output on the terminal timing signal (EIA-232 pin 24). Receive clocking is input through the receiver timing signal (EIA-232 pin 17). The transmitter timing signal (EIA-232 pin 15) is not used.
4: FMP Link Configuration Options To set this option using the DLI configuration file, use the protocol parameter; for example, protocol = “FMP”. See Figure 5–1 on page 104. 4.5 Parity Option (6) When using the ASCII/LRC-8 character set, this option controls the setting of bit 7 of each character. Parity can be set to odd, even, or none (space parity for bisynchronous).
FMP Programmer’s Guide 4.6.2 EBCDIC/CRC-16 When this setting is used, the FMP control sequences are transmitted in 8-bit EBCDIC format, and the CRC-16 block check polynomial is performed. The parity option is ignored when using EBCDIC/CRC-16. 4.6.3 ASCII/CRC-16 When this setting is used, the FMP control sequences are transmitted in 7-bit ASCII (space parity) format, and the CRC-16 block check polynomial is performed. Data parity checking is disabled when using ASCII/CRC-16. 4.6.
4: FMP Link Configuration Options characters. For example, a transmission block size of 512 bytes consists of 510 bytes of data plus two control characters (SOH and ETX). SYN, DLE, PAD, and BCC characters are not included in the transmission block size count. The FMP software automatically inserts all control characters in the blocks sent and removes them from blocks received.
FMP Programmer’s Guide If this option is set to disable, no data translation is performed. In this case, the client application program is responsible for performing any necessary data translation. The 5-bit Baudot-to-ASCII and ASCII-to-Baudot data translation using Translation Table 3 does not work in the same way as data translation using Translation Table 1.
4: FMP Link Configuration Options fit in one buffer. Data packing also helps move data from Freeway to the client more efficiently over the Ethernet. The default for this option is enabled. To disable this option using the DLI configuration file, use the dataPacking parameter; for example, dataPacking = “no”. See Table 5–1 on page 104.
FMP Programmer’s Guide Data Message Types: Only data buffers are packed. If a non-data buffer (such as a data acknowledgment or report) is placed on the waiting queue, data packing is temporarily interrupted. Data packing resumes when two sequential data type buffers appear on the queue. The buffer retains the command code of the first message in a packed buffer.
4: FMP Link Configuration Options figures show how the three example data blocks shown in Figure 4–6 on page 82 would be received for each option setting Message Blocking = Raw Blocks Data Packing = Enabled 3263 A B C D E F G H I J K L Figure 4–1: Data Packing Enabled (Message Blocking = Raw Blocks) Message Blocking = Data Records Data Packing = Enabled B E H K C F I L 3265 A D G J Figure 4–2: Data Packing Enabled (Mes
FMP Programmer’s Guide Message Blocking = Single Records Data Packing = Enabled 3267 A B C D E F G H I J K L Figure 4–3: Data Packing Enabled (Message Blocking = Single Records) Message Blocking = Data Records (With Header) Data Packing = Enabled 0 0 0 0 3269 06 00 A B C 06 01 D E F 06 02 G H I 06 02 J K L Note 5-byte header in this example = 06 00 0 Where: 06 = size of record including seq # and error code 00 = Simpact generated sequence number of block 0 = error code for record Figure 4–4: Data Pa
4: FMP Link Configuration Options Message Blocking = Raw Blocks (With Header) Data Packing = Enabled 0 A B C 0 D E F 0 G H I 3274 09 00 09 01 14 02 J K L Note 5-byte Where: 09 = 00 = 0 = header in this example: 09 00 0 size of block including seq # and error code Simpact generated sequence number of block error code for block Figure 4–5: Data Packing Enabled (Message Blocking = Raw Blocks with Header) 4.
FMP Programmer’s Guide 4.11 Modem Control Option (16) This option determines two things: the operation of the request to send (RTS) output modem signal and the detection of the data set ready (DSR) and data carrier detect (DCD) input modem signals. Table 4–2 lists the possible settings for this option.
4: FMP Link Configuration Options 4.11.2 DSR and DCD Signals Line activity ceases when the signal on the DSR pin is lost. With either the HDX-2 or FDX-2 setting, the incoming DSR signal is ignored by the FMP software. This setting is useful when DSR may not be present. 4.12 Feed ID Option (18) This option lets the application program assign a number to a configuration.
FMP Programmer’s Guide Table 4–3: Message Blocking Option Settings for Received Data Value Setting Description Freeway Data Codes 0 Raw Blocks Block is received with SOH, US, DLI_PROT_SEND_NORM_DATA and BCC characters left in DLI_PROT_SEND_NORM_DATA_EOM DLI_PROT_SEND_TRANS_DATA DLI_PROT_SEND_TRANS_DATA_EOM 1 Data Records BSC control chars are removed, DLI_PROT_SEND_NORM_DATA US chars are left in to separate DLI_PROT_SEND_NORM_DATA_EOM records DLI_PROT_SEND_TRANS_DATA DLI_PROT_SEND_TRANS_DATA_EOM
4: FMP Link Configuration Options To set this option using the DLI configuration file, use the messageBlocking parameter; for example, messageBlocking = “DataHdr”. See Table 5–1 on page 104. 4.13.1 Raw Blocks On inbound messages with Message Blocking set to Raw Blocks, FMP strips any leading PAD or SYN characters from the message. The FMP software also strips any trailing PAD characters from the message.
FMP Programmer’s Guide SOH data A US BCC data B ETX BCC User’s Outbound Message as Sent to FMP using the Raw Blocks Option PAD SYN SYN SYN SOH data A US BCC data B ETX BCC PAD Same Message with Characters Added by FMP Using the Raw Blocks Option Figure 4–8: Example of User’s Outbound Message (Raw Blocks Option) The Raw Blocks option is always used on asynchronous lines (line mode options 2–6).
4: FMP Link Configuration Options Message Blocking = Data Records Data Packing = Disabled D E F G H I J K L 3264 A B C Figure 4–9: Message Blocking Example (Data Records) data A US data B User’s Outbound Message as Sent to FMP using the Data Records Option PAD SYN SYN SYN SOH data A US BCC data B ETX BCC PAD Same Message with Characters Added by FMP Using the Data Records Option Figure 4–10: User’s Non-transparent Outbound Message (Data Records Option) DC 900-1339H 85
FMP Programmer’s Guide 4.13.3 Single Records Note The Single Records setting was added for compatibility with older versions of FMP on embedded ICP boards. This setting is not recommended for high-speed or multiple-line use on Freeway devices, as it generates more overhead on the Ethernet LAN. On inbound messages with the Message Blocking option set to Single Records, FMP strips out block check characters and all control characters including unit separators.
4: FMP Link Configuration Options 4.13.4 Data Records with Header On inbound messages with Message Blocking set to Data Records with Header, FMP strips out block check characters and all control characters including unit separators. Each individual record is preceded by a 5-byte header that contains information about the record. Figure 4–12 shows the format of the record header.
FMP Programmer’s Guide Message Blocking = Data Records (With Header) Data Packing = Disabled 06 01 0 D E F 06 02 0 G H I 06 02 0 J K L 3268 06 00 0 A B C Note 5-byte Where: 06 = 00 = 0 = header in this example = 06 00 0 size of record including seq # and error code Simpact generated sequence number of block error code for record Figure 4–13: Message Blocking Example (Data Records with Header) 4.13.
4: FMP Link Configuration Options Message Blocking = Raw Blocks (With Header) Data Packing = Disabled 09 01 0 D E F 14 02 0 G H I J K L 3273 09 00 0 A B C Figure 4–14: Message Blocking Example (Raw Blocks with Header) No header is required on outbound messages. See Figure 4–8 on page 84 for an example of transmitted data for this setting. 4.13.6 Message Blocking for the Bonneville Feed If the line mode option (Section 4.
FMP Programmer’s Guide 4.14 Block Checking Option (20) This option determines what characters are included in the block check character (BCC) calculation on transmitted and received data blocks. If the received block check character does not match the BCC value calculated by FMP, the DLI_ICP_ERR_BAD_BCC error code is returned to the client application. Block checking can be set to include or exclude the leading FMP control character or can be disabled completely.
4: FMP Link Configuration Options 4.15 Queue Limit Option (21) The queue limit option is used to prevent the ICP message buffer pool from being exhausted. Message buffers for all links on the ICP are taken from the same memory pool. This method allows each link to draw buffers as demand increases. However, if a process on the client were to stop reading on one link without disabling the link, incoming messages could deplete the buffer supply and the other links would not be able to obtain buffers.
FMP Programmer’s Guide 4.16 ETB Switch Option (24) The end of text block (ETB) switch option is normally set to disable, and all message blocks end in ETX. If you need blocks to end with ETB instead of ETX, enable this option. Then when a text block is too large and must be divided into smaller blocks, all blocks end in ETB except for the final block, which ends with ETX. To set this option using the DLI configuration file, use the etbEnable parameter; for example, etbEnable = “no”.
4: FMP Link Configuration Options To set this option using the DLI configuration file, use the lineMode parameter; for example, lineMode = “bsc”. See Table 5–1 on page 104. 4.19 Asynchronous Terminating Character Option (34) The asynchronous terminating character option allows you to define the terminating character for asynchronous communication. This configuration option is used only when the line mode is set to asynchronous or isochronous. See also Section 4.18.
FMP Programmer’s Guide Note This option applies only to asynchronous lines. To set this option using the DLI configuration file, use the usrDataRate parameter; for example, usrDataRate = 14. See Table 5–1 on page 104. 4.21.1 Example for Platforms other than the Freeway 1000 The Freeway PCLK frequency equals 7.3728 x 106.
4: FMP Link Configuration Options 4.21.2 Example for the Freeway 1000 Platform The Freeway PCLK frequency equals 3.6864 x 106 for the Freeway 1000. An example follows for 14400 bits per second: 3684400 V = --------------------------- – 2 14400 × 32 V = 8–2 V = 6 4.22 Electrical Interface Option (40) The electrical interface option applies to the Freeway 1000 model only and allows the electrical interface for each link to be set.
FMP Programmer’s Guide 96 DC 900-1339H
Chapter 5 Note FMP Link Configuration Using dlicfg In this document, the term “Freeway” can mean either a Freeway server or an embedded ICP. For the embedded ICP, also refer to the user’s guide for your ICP and operating system (for example, the ICP2432 User’s Guide for Windows NT). 5.1 Configuration Overview Section 3.1.1 on page 36 summarized your choices for performing ICP link configuration.
FMP Programmer’s Guide The DLI and TSI configuration process is a part of the loopback testing procedure described in Appendix D and the installation procedure described in the Freeway User’s Guide. During your client application development and testing, you might need to perform DLI and TSI configuration repeatedly. The DLI and TSI configuration procedures are summarized as follows: 1.
5: FMP Link Configuration Using dlicfg tsicfg TSI-text-configuration-filename [TSI-binary-configuration-filename] VMS example: tsicfg fmpaltcfg UNIX example: freeway/client/op-sys/bin/tsicfg fmpaltcfg NT example: freeway\client\op-sys\bin\tsicfg fmpaltcfg 5. From the freeway/client/test/fmp directory, execute dlicfg with the text file from Step 2 as input.
FMP Programmer’s Guide 7. If you have a VMS system, run the move.com command file from the [FREEWAY.CLIENT.TEST.FMP] directory. This moves the DLI and TSI binary con- figuration files you created in Step 4 and Step 5 into the bin directory for your particular TCP/IP package.
5: FMP Link Configuration Using dlicfg Application dlicfg DLI DLI Text Configuration File DLI Configuration Preprocessor DLI Binary Configuration File TSI 2836 tsicfg TSI Text Configuration File TSI Configuration Preprocessor TSI Binary Configuration File Transport Environment Figure 5–1: DLI and TSI Configuration Process DC 900-1339H 101
FMP Programmer’s Guide 5.2 DLI Session Configuration The DLI text configuration file used by the dlicfg program consists of the following sections: • A “main” section which specifies the DLI configuration for non-session-specific operations (described in the Freeway Data Link Interface Reference Guide) • One or more additional sections, each specifying a protocol-specific session associated with a particular Freeway serial communication link (port).
5: FMP Link Configuration Using dlicfg main { asyncIO = “no”; tsiCfgName = “fmpaltcfg.
FMP Programmer’s Guide Table 5–1: FMP ICP Link Parameters and Defaults for Using dlicfg dlicfg Option Name Default Valid Values dataRate 9600 75, 110, 135, 150, 300, 600, 1200, 2400, 4800, 9600, 19200, 38400 or 56000 clockSource “external” “external” or “internal” numLeadSync 3 2–8 protocol “FMP” “FMP” parity “odd” “none”, “odd”, or “even” charSet “asciilrc8” “asciilrc8”, “ebcdiccrc16”, “asciicrc16”, “asciilrc8bit6”, “ebcdicccitt0” or “asciiccitt0” transBlkSize 512 64–4096 dataTransl
Appendix A Line Control Procedures This appendix defines line control procedures for the FMP package. A.1 DSR Up/Down Reporting If the data set ready (DSR) signal is lost while a link is active, FMP suspends line operations for that link and notifies the client with the DLI_PROT_RESP_ERROR error report containing the DLI_ICP_ERR_DSR_DOWN error code. At that time, all ICP message buffers that are queued for transmission are discarded.
FMP Programmer’s Guide A.3 Modem Control Lines Table A–1 lists the EIA-232 modem control lines used by the FMP software. Table A–1: EIA-232 Modem Control Lines Signal Pin Direction Description RTS 4 Output For half-duplex, RTS is turned on just before transmission is started and turned off when transmission is complete. CTS 5 Input CTS is checked after RTS is turned on but prior to transmit.
A: Line Control Procedures Table A–2 defines the EIA-232 clock signals used by the FMP software.
FMP Programmer’s Guide 108 DC 900-1339H
Appendix B ASCII Translation Tables The FMP software contains ASCII/EBCDIC, ASCII/Baudot level-5, and ASCII/Baudot level-6 translation tables. Each table may be modified using software commands. Table B–1 through Table B–6 show the contents of the three translation tables immediately after the communications server download.
FMP Programmer’s Guide Table B–1: ASCII to EBCDIC Translation Table 1 0 1 2 3 4 5 6 7 8 9 A B C D E 0 20 45 2F 41 70 53 49 55 77 44 52 4A 4E 46 43 4B 1 54 5A 4C 57 48 59 50 51 4F 42 47 26 4D 58 56 72 2 2E 35 63 31 2E 73 67 00 30 34 74 79 00 36 33 2E 3 7C 7D 74 7B 38 5D 73 5B 00 32 37 42 53 7E 5E 00 4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
B: ASCII Translation Tables Table B–2: EBCDIC to ASCII Translation Table 1 0 1 2 3 4 5 6 7 8 9 A B C D E 0 00 01 02 03 9C 09 86 7F 97 8D 8E 0B 0C 0D 0E 0F 1 10 11 12 13 9D 85 08 87 18 19 92 8F 1C 1D 1E 1F 2 80 81 82 83 84 0A 17 1B 88 89 8A 8B 8C 05 06 07 3 90 91 16 93 94 95 96 04 98 99 9A 9B 14 15 9E 1A 4 20 A0 A1 A2 A3 A4 A5 A6 A7 A8 5B 2E 3C 28 2B 21 5 26 A9 AA AB EC AD AE AF B0 B1 5D 24 2A 2
FMP Programmer’s Guide Table B–3: ASCII to 6-bit Baudot Translation Table 2 0 1 2 3 4 5 6 7 8 9 A B C D E 0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2 00 00 00 00 00 00 1B 00 00 00 00 00 00 00 20 02 3 28 23 39 2E 29 21 2D 3A 34 00 00 00 00 00 00 00 4 00 03 19 0E 09 01 0D 1A 14 06 0B 0F 12 1C 0C 18 5 16 17 0A 05 10 07 1E 13 1D 15 11 37 00
B: ASCII Translation Tables Table B–4: 6-bit Baudot to ASCII Translation Table 2 0 1 2 3 4 5 6 7 8 9 A B C D E 0 20 45 2F 41 70 53 49 55 77 44 52 4A 4E 46 43 4B 1 54 5A 4C 57 48 59 50 51 4F 42 47 26 4D 58 56 72 2 2E 35 63 31 2E 73 67 00 30 34 74 79 00 36 33 2E 3 7C 7D 74 7B 38 5D 73 5B 00 32 37 42 53 7E 5E 00 4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5 00 00 00 00 00 00 00 00 00 00 00 00
FMP Programmer’s Guide Table B–5: ASCII to 5-bit Baudot Translation Table 3 0 1 2 3 4 5 6 7 8 9 A B C D E 0 00 00 00 00 00 00 00 87 00 00 00 02 00 08 00 00 1 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 2 04 00 13 00 9A 8D 00 85 8F 92 00 91 8C 83 9C 00 3 96 97 93 81 8A 90 95 87 86 98 8E 00 00 9E 00 9D 4 00 03 19 0E 09 01 0D 1A 14 06 0B 0F 12 1C 0C 18 5 16 17 0A 05 10 07 1E 00 1D 15 11 00 00
B: ASCII Translation Tables Table B–6: 5-bit Baudot to ASCII Translation Table 3 0 1 2 3 4 5 6 7 8 9 A B C D E 0 00 45 0B 41 20 53 49 55 0D 44 52 4A 4E 46 43 4B 1 54 5A 4C 22 48 59 50 51 4F 42 47 00 4D 58 56 00 2 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 3 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 4 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 5 00 00 00 00 00 00 00 00 00 00 00 00
FMP Programmer’s Guide 116 DC 900-1339H
Appendix C Error Codes There are several methods used by the DLI and FMP software to report errors (Table C–1 lists the FMP errors). 1. The error code can be returned directly by the DLI function call. Typical errors are those described in the Freeway Data Link Interface Reference Guide. 2. The FMP errors listed in Table C–1 can be returned in the global variable iICPStatus. The DLI constants are defined in the file dlicperr.h. 3.
FMP Programmer’s Guide 6. Under certain communication line conditions that cause queued transmission buffers to be discarded (such as losing the DSR signal while transmitting data), the FMP error can be reported in a data acknowledgment response to a dlRead request. In this case, the returned dlRead pOptArgs.usProtCommand field is set to DLI_PROT_RESP_LOCAL_ACK, and the dlRead pOptArgs.iICPStatus field is set to the actual error code.
C: Error Codes Table C–1: FMP Error Codes (Cont’d) 5-byte Header Freeway Code Code Techpubs — The 3 missing codes in column one are OK, per Fred Dickson. DLI Constant Name Meaning 9 –109 DLI_ICP_ERR_XMIT_TIMEOUT The protocol software was unable to transmit the data. This error occurs when some or all of the modem signals are not present. 10 –110 DLI_ICP_ERR_DSR_UP The protocol software has received a positive data set ready (DSR) signal from the remote station.
FMP Programmer’s Guide Table C–1: FMP Error Codes (Cont’d) 5-byte Header Freeway Code Code DLI Constant Name Meaning 45 –125 DLI_ICP_ERR_NO_CTRL_SESS No non-Control session is registered for this link. The operation is not allowed.
Appendix D FMP Loopback Test Program Note In this document, the term “Freeway” can mean either a Freeway server or an embedded ICP. For the embedded ICP, also refer to the user’s guide for your ICP and operating system (for example, the ICP2432 User’s Guide for Windows NT). D.1 Loopback Test Programs The FMP loopback test programs and test directories are listed in Table D–1, according to operating system (UNIX, VMS, or Windows NT).
FMP Programmer’s Guide To run the test program, perform the following steps: 1. Make sure the server TSI configuration parameter is correctly defined in the TSI text configuration file for each TSI connection definition. Refer to the Freeway Transport Subsystem Interface Reference Guide. 2. Make any required changes to the DLI text configuration file for DLI session parameters or ICP link parameters whose values differ from the defaults (for example, the elecInterface parameter for a Freeway 1000).
D: FMP Loopback Test Program For NT: nmake -f makefile. all where is the operating system: ant (for Alpha NT) int (for Intel NT) NT example: nmake -f makefile.ant all The make file automatically performs the following: • In VMS systems only, creates the foreign commands used for the dlicfg and tsicfg configuration preprocessor programs. (This is not necessary for UNIX and NT systems.) • Runs the dlicfg and tsicfg configuration preprocessor programs.
FMP Programmer’s Guide 5. Boot the Freeway server and load the FMP protocol software onto the ICP (refer to the Freeway User’s Guide). 6. Connect two ICP links with loopback cables (refer to the Loopback Test Procedures document). 7. Execute the test program from the directory where the binary DLI and TSI configuration files reside (that resulted from Step 4 above). In Step 4 above, the make file runs the dlicfg and tsicfg preprocessor programs and compiles and links the test program.
D: FMP Loopback Test Program • After you run dlicfg and tsicfg, run the move.com command file which moves the DLI and TSI binary configuration files to the bin directory for your TCP/IP package. @MOVE filename where filename is the name of the binary configuration file and is your TCP/IP package as shown above. VMS example: @MOVE FMPALDCFG.
FMP Programmer’s Guide 126 DC 900-1339H
Index A Access modes 32, 34 control 33 manager 33 shared manager 33 user 33 Acknowledgments local ack 57, 58, 60, 105, 118 Addressing Internet 22 ASCII character code 31 ASCII translation tables see Translation tables Asynchronous market feeds 24, 29 structured frame 30 terminating character 30 terminating character option 93 unstructured frame 30 Audience 11 B Baudot character code 31 Baudot translation tables see Translation tables Binary configuration files 22, 98 Bisynchronous market feeds 24, 28 Bit n
FMP Programmer’s Guide DLI_PROT_CFG_LINK 49 DLI_PROT_CLR_STATISTICS 47 DLI_PROT_SEND_BIND 50 DLI_PROT_SEND_UNBIND 51 DLI_PROT_SET_BUF_SIZE 48 DLI_PROT_SET_TRANS_TABLE 47 Commands foreign 98, 123 see dlWrite Communications software 23 Configuration 36 binary files 98 DLI alwaysQIO parameter 38 asyncIO parameter 38 cfgLink parameter 40, 48, 49 elecInterface parameter 122 enable parameter 40, 48, 49 example 103 localAck parameter 57, 58, 60 main section 102 mode parameter 32 msgBlkSize parameter 48 protocol pa
Index receive transparent data 60 send normal data 58 send transparent data 59 Data acknowledgement 57, 58, 60, 105, 118 Data acknowledgment 63 see Response codes Data codes 46 DLI_PROT_RECV_PACKED_DATA_EOM 87 DLI_PROT_SEND_NORM_DATA 58 DLI_PROT_SEND_NORM_DATA_EOM 58 DLI_PROT_SEND_TRANS_DATA 59 DLI_PROT_SEND_TRANS_DATA_EOM 59 Data link interface (DLI) 21, 22 Data packing option 74 Data rate option 68 Data records option 84 Data records with header option 87 Data transfer 57 Data translation option 31, 73 D
FMP Programmer’s Guide DLI_ICP_ERR_DSR_UP 105 DLI_ICP_ERR_INBUF_OVERFLOW 46 DLI_ICP_ERR_LINK_ACTIVE 49, 50, 51 DLI_ICP_ERR_LINK_INACTIVE 58 DLI_ICP_ERR_NO_TERM_CHAR 79 DLI_ICP_ERR_OUTBUF_OVERFLOW 46 DLI_ICP_ERR_QFULL 91 DLI_ICP_ERR_XMIT_TIMEOUT 58, 68, 118 FMP table of codes 118 iICPStatus global variable 117 list of codes 117 optArgs.
Index DLI_PROT_GET_LINK_CFG 54 DLI_PROT_GET_SOFTWARE_VER 57 DLI_PROT_GET_STATISTICS_REP 54 DLI_PROT_GET_STATISTICS_REPORT 54 DLI_PROT_GET_STATUS_REPORT 55 DLI_PROT_GET_TRANS_TABLE 56 Internet addresses 22 I/O blocking vs non-blocking 38 Isochronous market feeds 24, 31 L LAN interface processor 18 Letter-shift character 74 Line control procedures 105 clock signals 106 DSR up/down reporting 105 Freeway/line interface 105 idle line 107 modem control lines 106 Line mode option 27, 28, 30, 31, 92 Link 24 Link c
FMP Programmer’s Guide overview 17 support 16 Programs test 121 Protocol option 70 Protocol summary of FMP 27 Q Queue limit option 91 R Raw blocks option 83 Raw blocks with header option 88 Raw operation 37, 44, 45 Received data 60 Reference documents 12 Reports buffer 53 configuration 54 error 63, 105 statistics 54 status 55 translation table 56 Response codes 33 DLI_PROT_RECV_PACKED_DATA 79 DLI_PROT_RECV_PACKED_DATA_EOM 87 DLI_PROT_RESP_BIND_ACK 51 DLI_PROT_RESP_ERROR 33, 63, 105, 117 see also Error codes
Index see Configuration, TSI tsicfg preprocessor program 98 U UNIX configuration process 98 loopback test 121 Unstructured asynchronous frame 30 US character 81, 82, 84, 86, 87 User access mode 33 User-defined data rate option 93 V VMS configuration process 98 loopback test 121 VxWorks 18 W WAN interface processor 18 Windows NT configuration process 98 loopback test 121 writeType DLI parameter 45 DC 900-1339H 133
FMP Programmer’s Guide 134 DC 900-1339H
FMP Programmer’s Guide DC 900-1339H Customer Report Form We are constantly improving our products. If you have suggestions or problems you would like to report regarding the hardware, software or documentation, please complete this form and mail it to Simpact at 9210 Sky Park Court, San Diego, CA 92123, or fax it to (619)560-2838. If you are reporting errors in the documentation, please enter the section and page number.
Simpact, Inc.
