Gate Delay 3270 Chapter Three: The God Machine Nobody Talks About

The coffee stand had closed. Jamie’s laptop battery had died a noble but silent death. Alex had taken over the only working power outlet, and Sam had turned his hoodie into a pillow and was dozing lightly on the floor.

Frank, meanwhile, was rummaging through his bag like a man about to cast a spell.

“Behold,” he announced, dramatically producing… a printed diagram. Folded. Laminated. Possibly older than Jamie.

Jamie squinted. “Is that… a data flow map?”

“It’s the mainframe application topology from my last consulting gig,” Frank beamed. “I like to
keep a copy on me. It sparks joy.”

Dana arched an eyebrow. “That thing looks like a subway map designed by Escher.”

“Exactly,” Frank said proudly. “And every one of those lines? That’s a business-critical process.
Core banking. Payments. Inventory. Payroll. Identity management. Billing. Fraud detection. Oh—
and the ATM network.”

Jamie leaned in. “Wait—all of that’s on the same system?”

Frank grinned. “Yep. And it’s been running since before I had grey hair.”

Alex, now leaning across the armrest like a caffeinated raccoon, whistled. “So it’s a one-stop shop
for everything? That sounds… fragile.”

Frank shrugged. “Redundant hardware, dynamic workload management, near-zero downtime in production for decades. You’d be lucky if your Kubernetes cluster had that kind of track record.”

Dana snorted. “My CIO once bragged about 99.9% uptime for a cloud-based loyalty system.”
Frank didn’t miss a beat. “Mainframes scoff at 99.9%. That’s three nines. We play in the five-to-seven-nine league.”

Sam stirred, half-awake. “You’re saying this thing is more reliable than my hospital’s Wi-Fi?”

“It’s more reliable than oxygen in a board meeting,” Frank said. “It’s the Gordon Ramsay of
computing: intense, misunderstood, and absolutely essential under pressure.”

Suddenly, Dana’s tablet buzzed. A Slack message popped up from her digital transformation lead.

URGENT: Real-time analytics dashboard down. Backend not responding. Can’t
reach core data via API. Suspect token mismatch. Working theory: data not
syncing correctly from source.
Update: Trying to track source. Might be a nightly batch feed issue. System of
record is mainframe. No one knows who owns it. Thoughts?

Dana stared at it. Then sighed. Then slowly turned the screen to show the others.

Frank grinned like someone who’d just heard their favorite track at a party.

“Ah yes,” he said. “The Sacred Data Oracle strikes again.”

Alex leaned over. “Wait, are they saying the fancy new cloud dashboard is broken because… they
couldn’t talk to the mainframe?”

Jamie chuckled. “I thought the whole point of digital transformation was not depending on the old stuff.”

Dana rubbed her temples. “Apparently we’re transforming into a more sophisticated version of ‘we have no idea what we’re doing.’”

Frank leaned back, arms behind his head. “And there it is. The real problem isn’t the mainframe. It’s the fact that nobody knows how to talk to it. It’s become the wise old monk on the mountaintop—and all the kids are trying to climb up there with scooters and YAML payloads.”

Sam sat up, hair tousled, eyes bright with amusement. “So what you're saying is… the mainframe's fine. It's the humans who forgot how to read the runes.”

“Exactly,” Frank said. “It’s not legacy. It’s legendary.”

Dana looked down at the Slack message again. This time, there was the faintest twitch of a smile. “Well,” she said, tapping out a reply, “maybe it’s time we bring the monk down from the mountain and get it a better PR team.”