2003 and 2005 / KC5 finding 14
Old code outlived its use
Power Peg ceased use in 2003. In 2005 its cumulative-share tracking moved earlier in SMARS, without retesting Power Peg after the move. The old functionality remained callable. Finding 14.
July 27 onward / KC5 findings 12 to 17
Incomplete deployment
New RLP code for the planned August 1 NYSE launch was intended to replace Power Peg and repurposed its activation flag. Staged deployment updated 7 of 8 SMARS servers; the eighth retained old code. No second-technician review or required written review caught the omission. Findings 12 to 17.
August 1, from about 8:01 a.m. ET / KC5 finding 19
Premarket messages
Automated BNET reject e-mails identified “Power Peg disabled”; 97 reached personnel before the 9:30 a.m. ET open. They were not designed as alerts, generally were not reviewed on receipt, were not acted on before opening, and were not used to diagnose the problem afterward. Finding 19.
August 1, 9:30 a.m. ET opening / KC5 findings 16 to 17
The flagged parent orders
Orders with the repurposed flag ran correctly on the seven updated servers. On the eighth they activated defective old Power Peg. The different outcomes depend on which server received an incoming parent order. Findings 16 to 17.
August 1, about 45 minutes / KC5 findings 1, 17
Repeated routing and fills
From 212 incoming customer parent orders processed by defective code, SMARS sent millions of child orders, obtaining about 4,000,000 executions in 154 stocks for more than 397,000,000 shares. The introduction says over 4,000,000 executions. These are distinct counts: a routed child order is not necessarily an execution or a share. Routing lasted approximately 45 minutes. Introduction 1; finding 17.
August 1, during response / KC5 finding 27
Rollback worsened routing
Uninstalling new RLP code from the seven correctly updated servers caused further incoming parent orders to activate old Power Peg on those servers. The cited excerpt does not date that action more precisely. Finding 27.