Jack Ryan, Books 7-12 by Tom Clancy Page A

psychologist asked.
    Murray stood, to the surprised disappointment of the hovering waiter. “Now we drive down to headquarters and meet with Bill. We’ll get case agents in to set up a file. Bill and I and the case agent will walk across the street to the Department and meet with the Attorney General. After that, I don’t know exactly. We’ve never had one like this—not since the early seventies, anyway—and I’m not sure of procedure just yet. The usual stuff with your patient. Long, tough interviews. We’ll talk to Ms. Beringer’s family, friends, look for papers, diaries. But that’s the technical side. The political side will be touchy.” And for that reason, Dan knew, he’d be the man running the case. Another Holy shit! crossed his mind, as he remembered the part in the Constitution that would govern the whole procedure. Dr. Golden saw the wavering in his eyes and, rare for her, misread what it meant.
    “My patient needs—”
    Murray blinked. So what? he asked himself. It’s still a crime.
    “I know, Clarice. She needs justice. So does Lisa Beringer. You know what? So does the government of the United States of America.”
     
     
    He didn’t look like a computer-software engineer. He wasn’t at all scruffy. He wore a pinstriped suit, carried a briefcase. He might have said that it was a disguise required by his clientele and the professional atmosphere of the area, but the simple truth was that he preferred to look neat.
    The procedure was just as straightforward as it could be. The client used Stratus mainframes, compact, powerful machines that were easily networked—in fact they were the platform of choice for many bulletin-board services because of their reasonable price and high electronic reliability. There were three of them in the room. “Alpha” and “Beta”—so labeled with white letters on blue plastic boards—were the primaries, and took on the front-line duties on alternate days, with one always backing up the other. The third machine, “Zulu,” was the emergency backup, and whenever Zulu was operating, you knew that a service team was either already there or on the way. Another facility, identical in every way except for the number of people around, was across the East River, with a different physical location, different power source, different phone lines, different satellite uplinks. Each building was a high-rise fire-resistant structure with an automatic sprinkler system around the computer room, and a DuPont 1301 system inside of it, the better to eliminate a fire in seconds. Each system-trio had battery backups sufficient to run the hardware for twelve hours. New York safety and environmental codes perversely did not allow the presence of emergency generators in the buildings, an annoyance to the systems engineers who were paid to worry about such things. And worry they did, despite the fact that the duplication, the exquisite redundancies that in a military context were called “defense in depth,” would protect against anything and everything that could be imagined.
    Well, nearly everything.
    On the front service panel of each of the mainframes was an SCSI port. This was an innovation for the new models, an implicit bow to the fact that desktop computers were so powerful that they could upload important information far more easily than the old method of hanging a tape reel.
    In this case, the upload terminal was a permanent fixture of the system. Attached to the overall system control panel which controlled Alpha, Beta, and Zulu was a third-generation Power PC, and attached to it in turn was a Bernoulli removable-disk drive. Colloquially known as a “toaster” because its disk was about the size of a piece of bread, this machine had a gigabyte of storage, far more than was needed for this program.
    “Okay?” the engineer asked.
    The system controller moved his mouse and selected Zulu from his screen of options. A senior operator behind him confirmed that he’d made