Mainframe modernization assessments
Understand your mainframe job before you modernize it.
A clear, job-by-job assessment of your COBOL, JCL, and CICS: flow, data, dependencies, and plain-English explanations.
The problem
You can't safely move what nobody fully understands.
- The documentation is decades old, or it was never written.
- The people who know how the jobs really work are retiring.
- "Big bang" rewrites cost a fortune and have a reputation for failing.
- Without knowing what a job reads, writes, and calls, you can't estimate, plan, or test the move.
What you get
Before you move a mainframe job, know everything it touches.
I use an analysis tool I built for this work, then review every result myself. You get the full picture of each job or transaction you choose.
Everything read correctly
COBOL programs, copybooks, JCL, PROCs, CICS definitions, and BMS maps, straight from your own libraries.
Inventory
What's there and how big it is: programs by type, Db2, IMS, and MQ usage, and the largest and most complex members.
Job and program flow
Job steps and PROC overrides, CALL, XCTL, and LINK chains, and screen-to-screen flow for CICS transactions.
Data access
Which programs create, read, update, or delete each file and table, and how data moves from one job to the next.
Modernization findings
Complexity, dead code, and everything a job reaches outside its own scope: shared datasets, shared copybooks, other callers.
Plain-English explanations
What each job and program actually does, written for your team and reviewed by an engineer with 27 years of mainframe experience.
A report you keep
One self-contained HTML and PDF report, yours to share with your team and your migration partner. No dashboard that disappears when the contract ends. Here's a snapshot from a real one, for a single batch job:
POSTTRAN, the daily transaction posting job. It checks the day's card transactions, rejects the ones that fail (unknown card, missing account, over the limit, expired), and posts the rest to the transaction master and the account balances.
- 1COBOL program (CBTRN02C)
- 5copybooks
- 6datasets read, updated, or created
- 12record layouts
- 697lines of source
- 49decision points to test
Swipe sideways to see the whole diagram.
View the full POSTTRAN report · All sample reports
From my sample assessment of AWS CardDemo, a public, open-source mainframe credit card application (Apache License 2.0). No client code is involved.
How it works
Job by job, not all or nothing.
You choose where to start. Answers come in days, not a six-month discovery phase.
-
You choose the scope
Name the batch jobs or CICS transactions you want to understand first.
-
I get the source
Through a read-only user ID or a source extract, under written confidentiality terms.
-
Analysis and review
The tool maps everything the job reaches; I review and explain it.
-
Report walkthrough
We go through the findings together, and the report is yours to keep.
Prefer no AI at all? Choose the "map only" option: the inventory, flow, and data maps are produced entirely on my own machine, and none of your code is sent to any AI service.
Why work with me
Explained by someone who's done the work.
I'm an independent mainframe engineer with 27 years of hands-on experience building and supporting enterprise COBOL, JCL, CICS, and Db2 systems, working through Simon Solutions, LLC.
- Scoped to what you choose, so you only pay for what you need.
- Your code stays under your control: read-only access or an extract, handled under written confidentiality terms.
- A finished report you keep, in HTML and PDF.
- Help doesn't stop at the report. After the conversion, I'm available to answer questions, compare the new system's behavior with the old, and explain what the original COBOL did.
Pricing
A fixed price, agreed up front.
Every job is different, so let's talk about yours. Tell me which jobs or transactions you'd like to start with, and I'll send a fixed quote.
Contact
Let's talk about your first job.
Send me a note about what you're running and what you're planning. I'll reply within two business days.