# FIX Tag 35=q OrderMassActionRequest & Kill-Switch APIs

> Engineering FIX 5.0 SP2 OrderMassActionRequest (35=q), OrderMassActionReport (35=r), CME Globex Kill Switch, and Nasdaq/Cboe mass-purge vs O(N) cancel loops.

Canonical: https://terminalledgerdesk.com/reports/order-mass-action-request-fix-tag-35-q-firm-level-kill-switch-apis
Last updated: 2026-11-15T23:07:40.175Z

**Publication:** Terminal Ledger Desk
**Category:** Mifid Rts6 Pretrade Kill Switch Controls
**Published:** 2026-11-13T14:50:25.915Z
**Author:** Marcus Thorne, CQF (Certificate in Quantitative Finance (CQF), Low-Latency FIX & Matching Engine Architect)
**Reviewer:** Not recorded

## Answer-first summary

Iterating through 4,000 individual OrderCancelRequest (35=F) messages trips exchange message throttles right when seconds matter; FIX 35=q and SBE MassAction529 purge entire books atomically in under 1.5 milliseconds.

## Key takeaways

- Never rely on O(N) individual OrderCancelRequest (35=F) loops for emergency halts; venue message throttles delay full book cleanup for multiple seconds.
- FIX Tag 35=q (OrderMassActionRequest) and binary equivalents (CME SBE 529, Cboe Purge Ports) clear thousands of resting quotes atomically in ~1 millisecond.
- Always transmit emergency 35=q frames over a dedicated, idle Purge/Admin session so head-of-line blocking behind queued toxic orders cannot delay execution.
- Combine 35=q order purging with an exchange RMI / Clearing Hard Block so a crashed restart loop cannot immediately repopulate the order book.

## Related financial entities

- **CME Aurora Financial Data Center Standard** (CME-AURORA) — product: Dedicated CME Group hosting facility in Aurora, Illinois, housing the Globex matching engine and offering direct low-latency colocation to clearing members.
- **Electronic Trading Pre-Trade Risk Standard (FIA / CFTC)** (PRE-RISK) — product: Industry benchmark and regulatory requirement mandating automated pre-trade risk checks to prevent erroneous orders and systemic flash crashes.
- **Financial Information eXchange (FIX) Protocol Standard** (FIX-STANDARD) — product: Universal electronic messaging standard that facilitates real-time communication of securities transactions and market data across global financial institutions.

## Analysis

Suppose a multi-symbol futures or equity strategy holds **3,200 resting limit orders** across 60 instruments when a pricing model divides by zero. Attempting to flatten open exposure by firing 3,200 individual `OrderCancelRequest (35=F)` packets hits venue message-rate throttles (`500 to 1,500 msg/sec`) and stretches cleanup across **2 to 6 full seconds**! Institutional kill switches eliminate `O(N)` cancel storms using single-packet **atomic mass-purge primitives**: **`OrderMassActionRequest (35=q)`** / **`OrderMassActionReport (35=r)`** (`CME iLink 3 OrderMassActionRequest529`) and dedicated clearing-firm Kill Switch APIs.

## Why `35=q` (`OrderMassActionRequest`) Superseded Legacy `35=q` (`OrderMassCancelRequest`)

In classic FIX 4.2/4.4, `MsgType 35=q` was named `OrderMassCancelRequest` (`MassCancelRequestType Tag 530`). Starting in **FIX 5.0 SP1/SP2** under the [FIX Protocol Messaging Standard](/engines/fix-protocol-messaging-standard)—and adopted natively by CME Globex iLink 3, Eurex T7, and Cboe—`35=q` evolved into **`OrderMassActionRequest`**, introducing two critical tags covered in our [MiFID II RTS 6 & SEC 15c3-5 Architecture Hub](/reports/mifid-ii-rts-6-sec-rule-15c3-5-pretrade-risk-kill-switch-sla-guide):
- **`MassActionType (Tag 1373)`**: Supports not only `3 = Cancel orders`, but also `0 = Suspend orders`, `1 = Release orders from suspension`, and venue-specific **Order Entry Freeze + Cancel** combinations!
- **`MassActionScope (Tag 1374)`**: Targets surgical blast radii in a single frame: `1 = All orders for a Security`, `2 = All orders for an Underlying`, `6 = All orders for a Trading Session`, `7 = All orders` across the entire executing firm/account, or `9 = Market Segment ID` (`Tag 1300`)!

![Head-of-line blocking trap on a congested primary order socket vs zero-queue out-of-band dedicated Kill-Switch session dispatching FIX 35=q across matching partitions](/api/figure?type=flow&title=Out-of-Band%20Dedicated%2035%3Dq%20Kill-Switch%20Session%20Topology&subtitle=Bypass%20saturated%20primary%20TX%20queues%20via%20an%20idle%20secondary%20session%20%2B%20RMI%20Entry%20Block&steps=1.%20Anomaly%20Trigger%3A%3ALoop%20or%20VaR%20breach%20detected%20in%2050%20us%7C2.%20Local%20TX%20Squelch%3A%3ADrop%20primary%20NIC%20TX%20%2F%20stomp%20FPGA%20FCS%7C3.%20Idle%20Kill%20Session%3A%3AFire%20parallel%2035%3Dq%20across%20segments%7C4.%2035%3Dr%20%2B%2039%3D4%20Audit%3A%3AVerify%20TotalAffectedOrders%20%3D%3D%20OpenCnt&metrics=SINGLE%2035%3DQ%20SIZE%3A%3A84%20Bytes%3A%3ACME%20iLink%203%20SBE%20MassAction529%7CPURGE%20LATENCY%3A%3A0.8%E2%80%931.4%20ms%3A%3A3%2C200%20orders%20cleared%20atomically%7CTHROTTLE%20EXEMPT%3A%3AYes%3A%3ANever%20blocked%20by%20OTR%20caps!%7CENTRY%20BLOCK%3A%3ARMI%20Freeze%3A%3APrevents%20immediate%20re-quoting)

## CME Globex Kill Switch vs `OrderMassActionRequest529`: Two Distinct Layers

Inside [CME Aurora DC3](/engines/cme-aurora-colocation-standard), traders must distinguish two complementary emergency tools:
1. **In-Band `OrderMassActionRequest529` (`35=q`)**: Sent over an active iLink 3 SBE session (`1 single 84-byte packet`, exempt from messaging-efficiency surcharges!). Sweeps matching orders by `MarketSegmentID`, `InstrumentGroup`, `Session`, or `Account`, optionally filtering by `Side` or `OrdType (Day vs GTC)`, and returns `OrderMassActionReport562 (35=r)` listing `TotalAffectedOrders (Tag 533)` in **`0.6 to 1.4 ms`**.
2. **CME Globex Firm-Level Kill Switch (`CME Risk Management Interface / RMI` & GUI)**: Triggered by the executing firm or clearing FCM ([CFTC Reg 1.73 clearing screens](/reports/cftc-reg-1-73-fcm-automated-clearing-credit-screen-latency-mandates)). Simultaneously **blocks ALL new inbound `35=D` / `35=G` / `MassQuote` messages** across target `SenderCompID`s AND cancels all resting working orders (including `GTC/GTD`!) until an authorized risk officer explicitly sends an **Unblock** command!

| Kill-Switch Mechanism | Wire Complexity | Stops New Inbound Orders? | Throttle / OTR Penalty? | Typical Completion SLA |
| :--- | :--- | :--- | :--- | :--- |
| **Individual `35=F` Cancel Loop** | `O(N)` (`~550 KB` for 3k orders) | No (Strategy keeps firing) | **Counts against msg/sec caps!** | `1,500 – 5,000+ ms` |
| **In-Band `35=q` (`MassAction`)** | `O(Segments)` (`< 1 KB` total) | Cancels only (unless Freeze flag) | **Exempt** on major venues | `0.8 – 2.5 ms` (if queue empty) |
| **Dedicated Idle `35=q` Port** | `O(Segments)` (`0` queue wait) | Pair with local FPGA TX block | **Exempt** + zero HOL blocking | **`0.6 – 1.4 ms`** |
| **Venue RMI / Portal Kill Switch** | `1` HTTPS / FIX Admin call | **Yes (Hard MPID/Firm Freeze)** | Exempt (Admin control plane) | `8.0 – 35.0 ms` |

## `O(N)` Individual `35=F` Loop vs `35=q` Mass Action vs Venue RMI Kill Switch

Benchmarking wire bytes, throttle immunity, execution freeze guarantees, and completion time across 3,000 open orders.

```formula
T_purge_35F_loop = (N_open_orders / R_session_msg_limit_per_sec) + T_wire_rtt
T_purge_35q_idle = T_wire_rtt + (N_open_orders * T_engine_intrusive_unlink_ns)

Worked Purge Comparison for N_open_orders = 3,200 Quotes (R_limit = 1,000 msg/s, RTT = 0.65 ms, Unlink = 85 ns):
 Individual 35=F Loop = (3,200 / 1,000) s + 0.00065 s = 3.20065 seconds (3,200.65 ms!)
 Dedicated Idle 35=q = 0.65 ms + (3,200 * 0.000085 ms) = 0.65 ms + 0.272 ms = 0.922 milliseconds!
```

## Parsing `OrderMassActionReport (35=r)` & Reconciling `AffectedOrdGrp`

When `35=q` executes inside a partitioned matching engine (where e.g. `ES` runs on Market Segment `68` and `ZN` runs on Market Segment `54`), pay close attention to **partition scoping**:
- On CME iLink 3, a single `OrderMassActionRequest529` addresses **one `MarketSegmentID` at a time** (or `All` within a gateway partition); sweeping 8 market segments requires firing **8 parallel `529` packets (`672 bytes` total)** simultaneously!
- Watch **`MassActionResponse (Tag 1375)`**: `1 = Accepted` vs `0 = Rejected` (`MassActionRejectReason Tag 1376`). Never mark local OMS orders dead until either `AffectedOrdGrp (NoAffectedOrders Tag 534)` inside `35=r` OR individual unsolicited `35=8 (39=4 Canceled)` reports confirm every `ClOrdID`, preventing ghost position drift ([gross vs net intraday credit accounting](/reports/gross-vs-net-intraday-credit-exposure-accounting-pending-order-var)).

![Time required to cancel 3,200 resting orders across four methods: Dedicated SBE 35=q, REST RMI Kill Switch, Throttled 35=F Loop, and Head-of-Line Blocked 35=q](/api/figure?type=bars&title=Time%20to%20Purge%203%2C200%20Resting%20Orders%20Under%20Stress%20%28Milliseconds%29&subtitle=Why%20O%281%29%20dedicated%20binary%2035%3Dq%20outperforms%20O%28N%29%20individual%2035%3DF%20loops%20by%202%2C500x&steps=Dedicated%20Idle%20SBE%2035%3Dq%20Session%3A%3A1.1%20ms%20%28Parallel%20segment%20broadcast%29%7CClearing%20RMI%20REST%20API%20Kill%20Switch%3A%3A18.5%20ms%20%28HTTPS%20%2B%20Firm-wide%20freeze%29%7C35%3Dq%20Queued%20Behind%2010k%20Buggy%20Msgs%3A%3A840.0%20ms%20%28Head-of-line%20TX%20stall!%29%7C3%2C200%20Individual%2035%3DF%20%40%201k%2Fs%20Cap%3A%3A3%2C200.0%20ms%20%283.2s%20throttled%20bleed!%29&metrics=SPEEDUP%20VS%2035%3DF%3A%3A2%2C900x%3A%3A1.1%20ms%20vs%203%2C200%20ms%20loop%7CGTC%20INCLUSION%3A%3AConfigurable%3A%3ASet%20OrdType%20filter%20%3D%20All%7CDRILL%20FREQUENCY%3A%3AQuarterly%3A%3ARTS%206%20Art.%2012%20live%2FUAT%20test%7CRE-ENABLE%20AUTH%3A%3A2-Person%3A%3ARisk%20%2B%20Head%20Trader%20signoff)

## Dedicated Cancel/Kill-Switch Ports: Never Share a Congested Entry Socket!

If a runaway strategy has stuffed **12,000 `NewOrderSingle` messages** into the Linux kernel or NIC transmit ring buffer of `Session_1`, appending `35=q` to the **back** of `Session_1` FIFO queue means your kill switch sits behind 12,000 toxic orders!

Under our [Pre-Trade Risk Control Standard](/engines/pretrade-risk-control-standard), always provision a **dedicated, idle Secondary Kill-Switch Session (`Session_Kill`)** configured with Firm/Account-wide `MassActionScope`, paired with an out-of-band [Drop-Copy shadow kill switch](/reports/drop-copy-shadow-kill-switch-out-of-band-clearing-broker-disconnect). Model unhedged exposure during purge latency via the [Terminal Margin VaR & ES Calculator](/calculators/terminal-margin-var-es-calculator) and test session setups on [FIX API](/software/fix-api).

## Frequently asked questions

### What is a Cboe "Purge Port" and why do options market makers buy dedicated purge ports?

On Cboe Equities and Options (US/Europe), a Purge Port is a specialized BOE/FIX logical port dedicated exclusively to Mass Cancel / Purge frames across dozens of order-entry sessions simultaneously—bypassing normal per-port order queues so a market maker can pull 25,000 option strikes in ~1 millisecond!

### Why did one 35=q message on CME Globex cancel our ES futures but leave our 10-Year Treasury (ZN) orders live?

CME Globex partitions matching engines by MarketSegmentID (Tag 1300—e.g., Equity Index vs Interest Rates vs Energy). An iLink 3 OrderMassActionRequest529 must either iterate across every active MarketSegmentID in parallel or invoke the firm-wide CME Risk Management Interface (RMI) API.

### Does triggering an exchange-level Hard Kill Switch automatically allow an automated script to unblock 2 seconds later?

No—by regulatory design under MiFID II RTS 6 Article 12 and exchange rulebooks, unblocking a Firm-Level Kill Switch requires authenticated Risk Administrator intervention after verifying the runaway process is dead, preventing flapping re-entry loops.

### Should our OMS clear open orders locally the instant 35=q is written to the socket?

Never! Orders can still fill during the 450-microsecond one-way flight of 35=q to the matching engine. Wait strictly for OrderMassActionReport (35=r) and unsolicited 39=4 Canceled / 39=2 Filled ExecutionReports to settle exact terminal positions.


## Source URLs

- https://www.fixtrading.org/online-specification/order-mass-handling/
- https://www.cmegroup.com/confluence/display/EPICSANDBOX/iLink+3+Order+Mass+Action
- https://cdn.cboe.com/resources/membership/Cboe_US_Equities_BOE_Specification.pdf

## Citation

- APA: Marcus Thorne, CQF. (2026). FIX Tag 35=q OrderMassActionRequest & Venue Firm-Level Kill-Switch APIs Benchmarked. Terminal Ledger Desk. https://terminalledgerdesk.com/reports/order-mass-action-request-fix-tag-35-q-firm-level-kill-switch-apis
- Canonical article: [FIX Tag 35=q OrderMassActionRequest & Venue Firm-Level Kill-Switch APIs Benchmarked](https://terminalledgerdesk.com/reports/order-mass-action-request-fix-tag-35-q-firm-level-kill-switch-apis)
- Site research index: [Terminal Ledger Desk](https://terminalledgerdesk.com/llms-full.txt)
