The sys-con, working on his control console, brought Zulu on-line. At 16:10:00 EST, the backup machine started duplicating the jobs being done by Alpha, and simultaneously backed up by Beta. With one difference. The throughput monitor showed that Zulu was running slightly faster. On a day like this, Zulu normally tended to fall behind, but now it was running so fast that the machine was actually "resting" for a few seconds each minute.

"Smokin', Chuck!" the sys-con observed. Searls drained his water bottle, dropped it in the nearest trash bucket, and walked over.

"Yeah, I cut out about ten thousand lines of code. It wasn't the machines, it was the program. It just took us a while to figure the right paths through the boards. I think we have it now."

"What's different?" the senior controller asked. He knew quite a bit about software design.

"I changed the hierarchy system, how it hands things off from one parallel board to another. Still needs a little work on synchronicity, tally isn't as fast as posting. I think I can beat that in another month or two, cut some fat out of the front end."

The sys-con punched a command for the first benchmark test. It came up at once. "Six percent faster than two-point-three-point-one. Not too shabby."

"We needed that six percent," the supervisor said, meaning that he needed more. Trades just ran too heavy sometimes, and like everyone in the Depository Trust Company, he lived in fear of falling behind.

"Send me some data at the end of the week and maybe I can deliver a few more points to you," Searls promised.

"Good job, Chuck."

"Thanks, Bud."

"Who else uses this?"

"This version? Nobody. A custom variation runs the machines over at CHIPS."

"Well, you're the man," the supervisor noted generously. He would have been less generous had he thought it through. The supervisor had helped design the entire system. All the redundancies, all the safety systems, the way that tapes were pulled off the machines every night and driven upstate. He'd worked with a committee to establish every safeguard that was necessary to the business he was in. But the quest for efficiency—and perversely, the quest for security—had created a vulnerability to which he was predictably blind. All the computers used the same software. They had to. Different software in the different computers, like different languages in an office, would have prevented, or at the very least impeded, cross-talk among the individual systems; and that would have been self-defeating. As a result, despite all the safeguards there was a single common point of vulnerability for all six of his machines. They all spoke the same language. They had to. They were the most important, if the least known, link in the American trading business.

Even here, DTC was not blind to the potential hazard. ELECTRA-CLERK 2.4.0 would not be uploaded to Alpha and Beta until it had run for a week on Zulu, and then another week would pass before they were loaded onto the backup site, whose machines were labeled "Charlie," "Delta," and "Tango." That was to ensure that 2.4.0 was both efficient and "crash-worthy," an engineering term that had come into the software field a year earlier. Soon, people would get used to the new software, marvel at its faster speed. All the Stratus machines would speak exactly the same programming language, trade information back and forth in an electronic conversation of ones and zeros, like friends around a card table talking business. Soon they would all know the same joke. Some would think it a good one, but not anyone at DTC.