3985-parent-orders
| # | Message Name | Description |
|---|---|---|
| 3985 | SpdrAccntCancel | Records inserted into this table will result in the cancellation of all active/cancelable orders for the indicated SpiderRock trading accnt. |
| 3990 | SpdrBrokerCancel | Records inserted into this table causes the corresponding parent broker to cancel the current underlying parent order if active and cancellable. |
| 4000 | SpdrFixParentCancel | Records inserted into this table causes the corresponding parent order to be cancelled if it is active and cancellable. |
| 4005 | SpdrFixParentExecution | |
| 4010 | SpdrFixParentReject | Record indicates that either a SpdrParentOrder (Add or Replace) or FixParentCancel request failed |
| 4025 | SpdrMLegBrkrEvent | SpdrMLegBrkrEvent records are published when a new or clx/replace parent order arrives causes a broker to beging working and again when a parent order terminates and the underlying broker stops working. The initial version contains state and market data from just after the initial risk check and first attempt at generating child orders. |
| 4030 | SpdrMLegBrkrState | SpdrMLegBrkrState records are published by execution engines and describe the current state of a broker that is managing a SpiderRock parent order. These records include a description of the active child orders managed by the broker. Records are updated whenever a child order changes and also at other times but are not completely live and may not always reflect current market data or limit levels for working orders. |
| 4060 | SpdrParentBrkrDetail | SpdrParentBrkrDetail records are created/published by SpiderRock Execution Engines. Each record describes the current active detail of a single parent broker. |
| 4065 | SpdrParentBrkrEvent | SpdrParentBrkrEvent records are published when a new or cxl/replace parent order arrives causes a broker to begin working and again when a parent order terminates and the underlying broker stops working. The initial version contains state and market data from just after the initial risk check and first attempt at generating child orders. |
| 4070 | SpdrParentBrkrState | SpdrParentBrkrState records are created/published by SpiderRock Execution Engines. Each record describes the current state of one (or more) parent orders. If a parent order is canceled/replaced then entire chain is represented by a single broker state record. |
| 4075 | SpdrParentBrokerSummary | SpdrParentBrokerSummary records are created at the end of a trading period and contain a summary of trading activity for the period; Summary of Stk/Fut/Opt/MLeg Brkr State records. |
| 4080 | SpdrParentCancel | Records inserted into this table causes the corresponding parent order to be cancelled if it is active and cancellable. Either put in a custom datasource or deprecate from SRSE (Natively not allowed to be modified via SRSE) |
| 4085 | SpdrParentExecution | SpdrParentExecution records are published every time a parent order execution is received. They also update as additional post execution mark information is available at F+1m and F+10m. |
| 4090 | SpdrParentLimit | SpdrParentLimit records are supplied by clients (via SRSE) for use with parent orders having orderLimitType=Aux. This table can be updated either before or after a parent order begins working and will influence the limit(s) used when working child orders. Updates to this table do not constitute cancel/replace operations for the parent order. |
| 4095 | SpdrParentOrder | SpdrParentOrder records are visible in SRSE immediately after receipt. Parent orders received via FIX, SRSE or SpiderRock GUI tools, or 3rd party vendor systems are all visible in this table. Parent orders can be for stocks, futures, options or spreads. And they can be one-sided (agency) or two-sided (facilitation) orders. Parent order records should be immutable and not update. SpdrParentOrder records are published to the SpiderRock elatic cluster on arrival. |
| 4100 | SpdrParentReport | SpdrParentReport records contain the current state of a parent order and update as/when the order state changes. SpdrParentReport records are published to the SpiderRock elastic cluster when they reach a terminal state (closed, rejected, filled, etc.) |
| 4105 | SpdrReleaseWaitTrigger | SpdrReleaseWaitTrigger records are used to trigger the release of parent orders submitted with startType=WaitTrigger. Note that all parent orders in a risk group will be triggered together. |
| 1467 | SpdrRiskGroupCancel | Records inserted into this table causes the corresponding parent broker to cancel the current underlying parent order if active and cancellable. |
| 4110 | SpdrRouteCancel | Records inserted into this table will result in the cancellation of all active/cancelable orders for the indicated SpiderRock routing code |
| 4115 | SpdrSecKeyCancel | Records inserted into this table causes the corresponding parent broker to cancel the current underlying parent order if active and cancellable. |
| 4120 | SpdrSetActiveSize | SpdrSetActiveSize records control the active working size for parent orders that are locked (have active size controls). These records can be modified by ClientRiskTrader and ClientStageTrader user types. |
| 4135 | SpdrStripeTrigger | SpdrStripeTrigger records are used to allocate sweep risk and trigger cross stripe release of parent orders submitted with startType=WaitTrigger. These records are published by a SR Strategy Server if/when a SpdrReleaseWaitTrigger message is received. |
| 4140 | SpdrUserCancel | Records inserted into this table cancels all parent orders associated with userName/clientFirm |