Platform Connectivity & Overview
Static IP addresses of FIX engines must be white-listed in PMX. Contact support@qcex.com to request this and Sender/TargetCompID.Firm, User and Account Identifiers
The PMX Platform exposes two FIX gateways to participants; an order management gateway, and a second gateway to receive market data. Additional drop-copy sessions can be provided upon request. Note that should the Exchange offer direct market access (DMA) to their underlying customer, then each DMA customer should have their own dedicated pair of FIX gateways. An example FIX session configuration is shown below. Note the network details and Sender/TargetCompID (in red) will be provided by the exchange operator.Example QuickFIX session configuration
[DEFAULT] ConnectionType=initiator SocketConnectHost=12.12.12.12 SocketConnectPort=13001 BeginString=FIXT.1.1 DefaultApplVerID=9 SenderCompID=SENDERCOMP1 [SESSION] TargetCompID=EXCHANGECOMPID
The PMX platform also validates individual users (traders) using SenderSubID (50), and customer accounts using Account (1) which are validated on order entry. Please contact the exchange operator to allocate these codes.
Symbology
PMX uses a simple string identifier to instruments trading on the platform, which is required to identify instruments in the API using Symbol (55). There is currently no support to identify instruments using any other common identifiers such as CUSIP, ISIN or Bloomberg code. A list of instruments on the platform can be retrieved using the SecurityListRequest [x] message.Instrument States Instrument may the the following states:
Table 1: Instrument States
| State | Definition |
|---|---|
| PENDING | Initial state for a newly created instrument which has not yet begun trading. |
| OPEN | In this state, the instrument is open for continuous order entry and matching. |
| CLOSED | In this state, orders can not be entered, modified, or canceled, and no matching occurs. Any existing Day orders will be expired. |
| PREOPEN | Orders can be entered and modified, but no matching occurs. When the instrument transitions to an OPEN state, the orders entered during PREOPEN will match at a single opening price that is automatically determined by an algorithm that is designed to maximize the volume traded at the open. |
| MATCH_AND_CLOSE_AUCTION | This state is similar to PREOPEN, with the exception that matching will occur upon the transition of this state to any other state. This state is useful if you want matching to occur at the end of the state, but you don’t want the instrument to be open after. |
| SUSPENDED | Orders can be canceled but no matching occurs, and no order entry or modification is allowed. |
| HALTED | This state is similar to SUSPENDED, with the exception that orders cannot be canceled. |
| EXPIRED | An Instrument moves to this state when its Expiration Date/Time is reached. In this state, any resting orders are expired and no new orders can be entered. |
| TERMINATED | When an Instrument’s Termination Date is reached, the order book is removed from the matching engine, orders are canceled, and positions are closed. Historical data will still remain in PMX ledgers. |
FIX Notation
Please note the following presentation notes which apply to message definitions and FIX examples throughout this document.- FIX tag/value pairs are delimited within a TCP connection using the SOH (ascii character 1) character. Since this is a non-printable character, in this document we use the | character instead, and pad each pair with spaces to make them easier to use.
- Components are blocks of FIX tags which appear frequently in the specification (e.g. header and footers which appear on every FIX message). They are defined centrally for convenience and then referenced throughout the document using <> notation.
- Repeating groups of FIX tags appear in various messages. The depth of a repeating group is indicated using the → marker in FIX message definitions.
- References to individual FIX fields (or “tags”) are presented in italic font, with the tag number following the tag name. For example HeartBtInt (108).