5120-srse-gateway
# | Message Name | Description |
---|---|---|
5130 | AutoHedgeControlGateway | SpdrAutoHedgeControl contains autohedge / risk group control details. Can be uploaded from SRSE, created from ExecutionEngines, or created by SR tools. |
5135 | AwayStockLocateGateway | Records inserted into this table represent locates that clients have received away from SpiderRock. After validation, any away locate inserted into this table is turned into a StockLocateResponse record and appears in the StockLocateResponse table. |
5140 | ExternAggGroupGateway | This table allows clients to enter start-of-day positions, and quantity bot/sld today for each market. AggGroup is a code issued by SpiderRock to indentify the aggregation group that the reported positions and trades belong to. This will usually be your SpiderRock assigned ClientFirm code unless your firm has more than one aggregation unit. Note that start-of-day positions can be truncated if the truncation will not affect order marking. Contact SpiderRock support for details if this is what you intend. |
5145 | FutAwayTktGateway | FutAwayTktGateway inserts are validated and convered to away SpdrParentExecution records and published. If successfully published they will be visible in the SpdrParentExecution table and on SpiderRock GUI tools. Replaces are allowed but they are functionally identical to updates in that only the fillPrice and fillQuantity fields are actually changed. |
5150 | FutOrderGateway | Records inserted, updated, or replaced into the FutureOrderGateway table are validated and then converted to SpdrParentOrder records and forwarded to the appropriate execution engine for futher processing. Parent orders can be inserted as either active/ready or in a wait start mode that requires subsequent release. See the SpiderRock Execution Engine concept guide for more details. |
5155 | MLegOrderGateway | Records inserted, updated, or replaced into the MLegOrderGateway table are validated and then converted to SpdrParentOrder records and forwarded to the appropriate execution engine for futher processing. Parent orders can be inserted as either active/ready or in a wait start mode that requires subsequent release. See the SpiderRock Execution Engine concept guide for more details. |
5160 | OptAwayTktGateway | OptAwayTktGateway inserts are validated and convered to away SpdrParentExecution records and published. If successfully published they will be visible in the SpdrParentExecution table and on SpiderRock GUI tools. Replaces are allowed but they are functionally identical to updates in that only the fillPrice and fillQuantity fields are actually changed. |
5165 | OptOrderGateway | Records inserted, updated, or replaced into the OptionOrderGateway table are validated and then converted to SpdrParentOrder records and forwarded to the appropriate execution engine for futher processing. Parent orders can be inserted as either active/ready or in a wait start mode that requires subsequent release. See the SpiderRock Execution Engine concept guide for more details. |
5180 | ParentOrderGateway | Records inserted, updated, or replaced into the ParentOrderGateway table are validated and then converted to SpdrParentOrder records and forwarded to the appropriate execution engine for futher processing. Parent orders can be inserted as either active/ready or in a wait start mode that requires subsequent release. See the SpiderRock Execution Engine concept guide for more details. |
5185 | ParentOrderGatewayExt | Records inserted, updated, or replaced into the ParentOrderGatewayExt table are validated and then converted to SpdrParentOrder records and forwarded to the appropriate execution engine for futher processing. Parent orders can be inserted as either active/ready or in a wait start mode that requires subsequent release. See the SpiderRock Execution Engine concept guide for more details. |
5190 | SecDefRequestGateway | |
5220 | StkAwayTktGateway | StkAwayTktGateway inserts are validated and convered to away SpdrParentExecution records and published. If successfully published they will be visible in the SpdrParentExecution table and on SpiderRock GUI tools. Replaces are allowed but they are functionally identical to updates in that only the fillPrice and fillQuantity fields are actually changed. |
5225 | StkOrderGateway | Records inserted, updated, or replaced into the StockOrderGateway table are validated and then converted to SpdrParentOrder records and forwarded to the appropriate execution engine for futher processing. Parent orders can be inserted as either active/ready or in a wait start mode that requires subsequent release. See the SpiderRock Execution Engine concept guide for more details. |
5230 | StockLocateRequestGateway | Records inserted into this gateway become locate requests and are visible in the StockLocateRequest table. |
5235 | ULinkContextGateway |