Field | Name | Type | Req'd | Comments | Pedigree |
|---|---|---|---|---|---|
95 | Status code. Code 3001 indicates that the request was processed successfully. For other codes, see the Status Code list in the EMAPI HTML description. | ||||
343 | A textual description of the status code above. | ||||
525 | Status code for each leg of the request. Only used for batched requests. | ||||
445 | Generic single string reply | ||||
314 | Indicates whether the login was successful or not. | ||||
313 | Login specific status code. | ||||
296 | Indicates whether this system is a test system or not. | ||||
534 | The name of the system. | ||||
388 | The interval (in seconds) between partition heartbeats sent from the system. Partition heartbeats are sent out as Heartbeat events. | ||||
85 | The interval (in seconds) between which clients are expected to send in heartbeats. The client should use the TaxHeartbeatReq message to send in heartbeats. | ||||
335 | The maximum number of heartbeats to lose before the connection can be considered to be down. |
Orchimate Copyright 2026 Atomic Wire Technology Limited
Orchestra Copyright 2026 FIX Protocol Ltd
Terms of Use|Privacy Policy