Skip to content

OpenVMS systems don't break often. But when they do, nobody knows how to fix them.

I help teams maintain, debug, and modernize OpenVMS systems. No risky rewrites. No guesswork.

COBOL, RMS, Rdb, networking, integration with modern systems.

Talk to me about your system

You're sitting on something critical

OpenVMS systems still run critical infrastructure across banking, telecom, healthcare, and industry. They're stable, battle-tested, and often decades old.

But:

  • — The people who built them are retiring
  • — Documentation is incomplete or outdated
  • — Modern teams don't understand how they work
  • — Even small changes feel risky

And rewriting everything is usually a terrible idea.

Not just theory. I build and ship in this space

Product

OpenVMS RMS API

Co-authored a modern interface for working with RMS data from external systems.

Learn more

Speaking

OpenVMS Bootcamp

Clients

Active OpenVMS engagements

  • US regional banking (subsidiary of a publicly traded bank)
  • Agricultural industry association (US West Coast)
  • US automobile leasing (multi-state operations)
  • European industrial automation
  • Automotive manufacturing (Nordic)

Client names under NDA

Where I help

Debugging and incident resolution

When something breaks and nobody knows why.

Legacy system understanding

Reverse-engineering COBOL logic and data flows.

RMS and data handling

Working with Record Management Services files, indexed records, and data structures. RMS is a core part of OpenVMS data handling. It supports multiple record access patterns and is deeply embedded in most VMS applications.

Database migration

Oracle Rdb is in sustaining support only: no new patches, no bug fixes. I help teams migrate from Rdb and RMS to modern database systems (PostgreSQL, MySQL, Oracle DB) while preserving data integrity and business logic.

Integration

Connecting OpenVMS systems with modern APIs, services, and platforms.

Modernization without rewriting

Incremental improvements instead of risky full migrations.

How this works

1

You show me the system or the problem

2

I dig into it. Fast, no onboarding needed

3

I identify root cause or risk areas

4

I fix it or give you a clear path forward

No endless meetings. No theory. Just results.

What most people get wrong

— Rewriting is often more dangerous than maintaining
— RMS is not "just files". It's deeply embedded logic
— COBOL systems are not inherently bad. They're just misunderstood
— The biggest risk is loss of knowledge, not technology

How to work with me

Emergency Help

Something is broken and needs immediate attention.

System Audit

Understand risks, architecture, and weak points.

Ongoing Support

Have someone who actually understands your system.

If your system feels fragile, it probably is.

Send me a short description of your setup or problem. I'll tell you quickly if I can help, and how.

or book a call