mainframe exit
Mainframe modernization: off COBOL and onto Go in 30 days
Your MIPS bill grows every year, and the one person who understands the batch is counting the days to retirement. Our engineers, 25+ years in production, move you to Go and Postgres in 30 days, matched to the cent.
Send the job streams today. In 48 hours you have a fixed price, a start date and the first stream to move.
JCL job graph, COBOL, 3270 screens, VSAM and DB2, and a licence bill that grows every renewal.
- BATCH.JCLJCL
- PAYCALCCOBOL
- CICS screens3270
- VSAM filesflat
- DB2z/OS
30 days to a full exit, the first job stream moved by day 7
Go services on an ordinary scheduler, Postgres, and a web client operators still drive by keyboard.
- batch runnerGo · cron
- paymentsGo
- web clientTypeScript
- postgresfrom VSAM + DB2
Off the mainframe one job stream at a time
- 01days 1–4
Inventory the job graph
Every JCL step, dataset and program it calls, as one graph. Plus what nobody mentions at kickoff: the 3am FTP job and the utility only one person can restart.
- 02days 3–8
Move the data model
Copybooks become typed structures, VSAM and DB2 become Postgres tables. EBCDIC, packed decimal and REDEFINES get settled here, at the start, where they cost least.
- 03days 6–26
Port each stream, run both
The first stream moves by day 7. Each one runs your inputs on the same night as the mainframe and takes over when the record-level diff is clean.
- 04days 24–30
Retire the region
CICS transactions move to the web client, the LPAR shrinks, and the MIPS and licence line comes off your budget. This is the part your CFO was asking about.
The platform parses COBOL, engineers own the answers
Parsing COBOL, JCL and copybooks
Platform
Every dialect quirk, including the copybook included eleven times with different REDEFINES.
Finding which programs are still alive
Both
Job logs answer most of it. For the rest we sit down with the person who remembers 2004.
Translating each program into Go
Platform
Reviewed as a pull request and rewritten by hand wherever the output still reads like COBOL.
Fixed-point arithmetic
Platform
Decimal stays decimal. A one-cent drift fails the comparison run, and the stream stays where it is.
Operator screens
Engineer
Built with the people who use them, keyboard-first, timed against their speed on 3270.
Batch window, cutover and the licence exit
Engineer
Which night, who holds the pager at 4am, and an exit timed to your vendor's contract dates.
The comparison run decides when a stream is ready. Nobody on either side gets to overrule it with an opinion.
Engineers who read COBOL for a living
Our engineers have written production code for more than 25 years, and they are the best people you can put on a mainframe exit. z/OS and AS/400, JCL batch and CICS, VSAM, DB2 and IMS, RPG and CL, packed decimal that has to land on the cent: dozens of migrations behind them. Your COBOL team talks to people who read the same code they do.
Fixed price before the first job moves, the exit date in the contract, and the code is yours. A stream that misses your production output by a cent is not accepted.
What mainframe owners ask us
Will the numbers match to the cent?
They have to, because that is how a stream gets accepted. COMP-3 becomes fixed-point decimal, floating point never touches money, and a one-cent difference fails the run. Send us your hardest payroll or ledger stream and we put it first.
What happens to our COBOL people?
They become the most important people on the project. Every migration hits a rule nobody wrote down, and they are the ones who know it. They move from keeping the lights on to deciding what is correct. Get a quote and bring them to the first session.
Why Go? Our platform team runs on Java.
A batch job that starts in milliseconds and ships as one static binary is easier to schedule and to debug at 3am. If your standard is Java, we write Java and the 30 days stay the same. Name your standard in the form and the plan is written for it.
How long do we run both systems in parallel?
Until the comparison is clean. Daily streams switch after a few clean nights. For month-end we replay the month you already recorded, so a quarterly close never holds up the date. Send the schedule and we show you which night each stream switches.
Do you do AS/400 as well?
Yes: RPG and CL, DDS-described files, 5250 green screens. The method is the same as on z/OS and the job graph is simpler, so the first stream moves even sooner. Send the library list today and get the price in 48 hours.
Start with your hardest job stream
Send us the stream today: what it does, when it runs and what breaks if it finishes late. In 48 hours you have a price and a date. The first stream moves by day 7, the whole mainframe by day 30.
Keep the scheduler open while you fill it in. The questions are about job streams and the batch window.