r/cobol • • 2d ago

COBOL and a programming career

39 Upvotes

Hello people of Reddit and cobol land, I would like to pick some folks brains about cobol and the future of the job market. Some background is I currently work in a factory, and while talking with a friend who does IT for a big bank, was talking about my job and them about theirs figured in the middle of this to mention at one point I had started to learn cobal because I thought I was a funny language to learn (no really) but didn’t get too far with it. My friend implored me to learn and that they would try as best they could to help me get a job, and that cobol would be a good place to start! Now it being 2026 soon to be 2027 I know the halcyon days of learn to do code and no degree devs are over. AI is king theses days it seems, and I would want to know, would it be worth going back and learning cobol to try and get a job no degree? Would AI not eventually come for those jobs too? Can I realistically expect to have a successful career and such doing this in this day and age? Thank you for all your help, I know these are big questions, and all help and comment is greatly appreciated!


r/cobol • • 4d ago

Toy COBOL compiler

30 Upvotes

One of the uni classes had a task to create a toy compiler. Since then I tweaked and tweaked and tweaked on it, and it became a bit larger project. In the last few days I've made some bigger code reorganization and cleanup, and actually learned to use git (hopefully) properly.

I've created the first release, it supports most of COBOL-85 on x86_64 on Linux and Windows, with the plan expand it to at least ARM and perhaps more.

I still don't know what constitutes as a good compiler even after reading a lot of books on compiler theory and so. Feedback would be welcome, also take the project as is, not as the future competitor for the title of "Favourite compiler of the global COBOL community" but rather as "people are interested in this stuff".

Go ahead and enjoy:

Release Cobalt 0.1.0-alpha · majormilan/cobalt


r/cobol • • 6d ago

DFSORT Emulation

Thumbnail
reddit.com
2 Upvotes

r/cobol • • 7d ago

Mainframe jobs abroad — how’s the market?

Thumbnail reddit.com
3 Upvotes

r/cobol • • 7d ago

Mainframe jobs abroad — how’s the market?

Thumbnail reddit.com
2 Upvotes

r/cobol • • 7d ago

Mainframe jobs abroad — how’s the market?

Thumbnail reddit.com
1 Upvotes

r/cobol • • 12d ago

Looking for Mainframe Developer Opportunities / Referrals (6 YOE | Bangalore & Pune) + Career Guidance

3 Upvotes

Hi everyone,

I'm a Mainframe Developer with around 6 years of experience, primarily in the Banking & Financial Services domain.

  1. Job Opportunities / Referrals

I'm actively looking for a Mainframe Developer / Mainframe Engineer opportunities in Bangalore or Pune or Remote.

My technical experience includes:

- COBOL, JCL, DB2 and VSAM

- Mainframe application development, maintenance and production support

- Batch processing, debugging, RCA and defect resolution

- FIS ALS-Systematics (Core Banking)

- IBM IDz, Git and basic CI/CD workflow exposure

- Agile and Waterfall methodologies

- Around 3 months of onsite experience in Belgium.

I'm particularly interested in organizations offering:

- Long-term project stability learning business logic in-out.

- Good exposure to development.

- Opportunities to learn and contribute to mainframe modernization initiatives.

- A healthy technical environment with decent career growth.

I'm currently serving my notice period. If you are aware of any relevant openings or can provide a referral, I'd genuinely appreciate your help.

2. Career Guidance & Interview Preparation

I'm also looking for suggestions from experienced mainframe professionals.

Recently, I've noticed that interviews are increasingly covering different areas:

- Scenario-based questions involving basics of COBOL, JCL, DB2 and VSAM, which we tend to miss at times.

- Real-time production issues, debugging and troubleshooting

- Mainframe modernization concepts, migration approaches, cloud integration, DevOps and CI/CD.

I'm trying to figure out how to prepare effectively and what skills to prioritize for long-term career growth.

A few things I'd love to hear your thoughts on:

- For someone with around 6 years of traditional mainframe development experience, what skills should I focus on to stay relevant?

- How deep should I go into modernization concepts?

- What are some good learning resources or hands-on projects to get started?

- How do you approach scenario-based interview preparation?

Would really appreciate any suggestions, referrals or experiences you could share.

Thanks in advance!


r/cobol • • 14d ago

I nearly started a holy war by asking a naive question about fixed-width files...

34 Upvotes

Junior dev here. A few days ago, I was looking at a massive, thousands-of-bytes-wide fixed-width text file dropping from upstream, where our downstream system only touches maybe 20 fields.

Innocently, I asked my mentor: "Why can't we just ask the upstream team to filter the layout and only send the 20 fields we actually need?"

She looked at me with pure horror and immediately shut me down before I got us both exiled to the shadow realm.

She explained the downstream blast radius, the sacred copybooks, and the bureaucratic nightmare of touching legacy batch pipelines. I completely understand and respect her reasoning—and I'm grateful she stopped me from making a fool of myself.

At the same time, this place is so heavily siloed and walled-off that it feels like its own isolated universe. It got me wondering: Is what she described an absolute, universal law across the entire enterprise/mainframe world, or is our specific shop just extraordinarily fragile and cursed?

If a clueless junior actually walked up to an upstream COBOL/mainframe team at your company and made that exact request... what would the fallout look like on your side of the fence?


r/cobol • • 16d ago

My new Video on COBOL ON SIZE ERROR usage

8 Upvotes

Hi, I have created a new video on Youtube on COBOL ON SIZE ERROR clause used in arithemtic operations to trap size ralted errors such as overflow/underflow/divide by zero/truncation during any arithmetic operation.

Here is the link to it:

https://www.youtube.com/watch?v=2jyx0sUC3zs

Do share in tyour comments


r/cobol • • 16d ago

My mistake - Doh !

Thumbnail reddit.com
2 Upvotes

r/cobol • • 17d ago

A Windows based ISPF Editor

3 Upvotes

Oct. 29, 2026

I have updated the Windows ISPF editor
It is available on the wincobol.com website  

How to Start using ZEDIT – a Windows based ISPF Editor  

Download ZEDIT_SPF.RTF from wincobol.com  

Rename it to ZEDIT_SPF.7Z

WIX, the website server, does not permit downloads of Windows executables – hence the .RTF  

Expand the .7Z archive into a drive and folder of your choice  

GOSPF.BAT is the method to execute the editor.

I have provided a 65K nonsensical COBOL example – APANEL.COB

 

To edit APANEL.COB:

·         Start a Windows CMD.EXE

·         Change the directory to where you have installed ZEDIT

·         Type GOSPF APANEL.COB – Press Enter

 

The edit session is now underway.

 

To exit use F3 or =X on the editor command line.

 

To edit your programs – GOSPF “your program name”

 

Help is available by using the F4 key.  

Help will explain the supported features and also using the 3270-keyboard simulation. 

Also, the IBM URL for the SPF Editor is:
https://www.ibm.com/docs/en/SSLTBW_3.1.0/pdf/f54em00_v3r1.pdf

I would start at:

Part 3. Command reference

 

Comments, bugs, or assistance is available via email.

[email protected]


r/cobol • • 19d ago

Do you know anyone that was laid off as a mainframe applications developer in the past 3 years?

8 Upvotes

I’m currently doing some research for an article I’m writing and need to get some info. If you know anyone or yourself that was recently laid off as a mainframe applications developer, can you explain why? Was it restructuring, wrongdoing, etc.


r/cobol • • 20d ago

I built a habit tracker where the web server, routing and HTML rendering are all written in COBOL

Thumbnail
youtu.be
17 Upvotes

COBOL turns 67 this year, so I wanted to see if it could run a modern-looking web app with nothing in front of it. No Node, no nginx, no CGI wrapper.

How it works

Server: COBOL calls libc’s socket/bind/listen/accept directly and forks a process per connection. Forking turned out to be necessary because Safari opens connections in advance and then sends nothing on them, which would freeze a server that handles one request at a time.

Routing: an EVALUATE statement, which is basically a switch on method and path.

Rendering: server-side with STRING ... WITH POINTER, so every page is built from string pieces in COBOL. User input gets HTML-escaped. Typing <script>alert(1)</script> as a habit name just shows up as text.

Zero JavaScript: every button is a plain <form method="post">, and the server answers with a 303 redirect back to / (POST/redirect/GET), so refreshing never resubmits anything.

Styling: one CSS file. The progress ring is a conic-gradient, and each habit’s color comes from color-mix().

Data: two text files with fixed-width records. Dates use COBOL’s INTEGER-OF-DATE, which honestly beats JavaScript’s Date.

It’s about 650 lines including comments, and the page reloads fast enough that you barely notice there’s no JS. To be clear, this is an experiment, not something to deploy. It’s macOS only, listens on localhost only, and has fixed limits like 100 habits max.

📺 Video walkthrough: https://youtu.be/lbkTRdpedS0

💻 Code: https://github.com/nick-friedrich/cobol-web-app

Happy to answer questions. Which old language should I try next?


r/cobol • • 21d ago

Looking to Transition into COBOL Development. Where Should I Start?

16 Upvotes

Hi everyone!
I’m looking to transition into COBOL development and would love some guidance from those already working in this field.
Where should I start? What should I study, which courses or resources are best, and how should I practice to become job-ready?
Any advice on learning COBOL, JCL, DB2, CICS, and mainframe basics, would be greatly appreciated.
I’m eager to learn and willing to put in the effort. Any guidance or personal experiences would mean a lot. Thank you! 🙏


r/cobol • • 21d ago

Is switching to HPE NonStop (Tandem COBOL) a good career move?

3 Upvotes

I have around 6 years of experience working on IBM mainframes, primarily with COBOL, JCL, DB2, and banking applications.

I'm considering an opportunity involving Tandem COBOL on the HPE NonStop platform and would like to understand its demand and long-term career prospects before making a decision.

For those who have worked with HPE NonStop or have experience in both ecosystems, I'd appreciate your insights on a few questions:

- Is Tandem COBOL still in demand?

- How does its job market compare with IBM mainframe development in terms of opportunities and career growth?

- Is it a good skill to build for the next 5–10 years, or is it becoming increasingly niche and would put me back in the race?

- Would switching after 6 years of IBM mainframe experience be a sensible career move, or could it limit my future opportunities?

I'm trying to understand whether this switch would be a good long-term decision or whether it would be better to continue building my expertise in IBM mainframes.

I'd appreciate honest opinions, especially from people currently working with these technologies or who have made a similar transition. Thanks!


r/cobol • • 23d ago

Why do people want to replace COBOL so badly?

98 Upvotes

I've been messing around with COBOL a bit, and honestly, the syntax seems pretty easy to understand.

I get that it's old and the ecosystem isn't as convenient as Python or JS, but is that really the main reason people move away from it?

Like, what if the tooling and libraries were actually nice to use? Would people be more open to it, or is there something fundamental I'm missing?


r/cobol • • 23d ago

Easy to use IDE for GnuCOBOL.

4 Upvotes

This is my easy to use IDE for GnuCOBOL.
This is WINIDE - its use is for PC targeted GnuCOBOL programs - as opposed to WINZOS for zOS emulation.
Break points can be set after successful compilation
OR
During runtime execution of the debugger
Both are demonstrated in the video

Compiling is simple, two choices, compile with animation (A) or without animation (M)
If a compilation error is detected the compile pane indicates compiled failed
Use a "V" function code to view the compilation listing
Find error by "F ERR 1"
Start a concurrent edit session - locate the error (from the compile listing), fix the error in the edit session, save the edit session, recompile.

If 'EXEC SQL' is detected in your COBOL source - the DB2 preprocessor and bind are done automatically.

Execution is initiated by eXecuting a .bat file "X"

The editor you use is extensible via an environment setting - the animation always uses the Xpediter like user interface.

The animated debugger is full featured. 
Right clicking a data field name will present a panel to display,  modify, watch . .   the selected data field.
Zoom "Z" animates the program at flank speed
Quite "Q" executes the program  sans the animation - break points are still honored

There are help screens with most of the WINIDE features

IMO it is the best GnuCOBOL IDE targeting PC based applications.
You can even animate programs having a screen section.

I will provide another post that targets zOS emulation

This iis the URL to view the video:

https://connect.flashbackrecorder.com/Default.aspx?id=2jEfosHvw9FyLSX5sI9N2g2

"The owner of this video requires you to login so they can track views."

If you got this message - I apologize - It is no longer necessary

Both WINIDE and WINZOS are available at wincobol.com

Both are FREE ! - No license fee - no maintenance fee


r/cobol • • 28d ago

COBOL: REDEFINES Clause

11 Upvotes

Mastering COBOL: The Power of the REDEFINES Clause

Ever wondered how to interpret the exact same chunk of memory in two completely different ways without allocating a single extra byte?

In mainframe applications, managing storage efficiently is everything. That is where the COBOL REDEFINES clause comes into play. It allows multiple data items to share the same physical memory space, giving you the flexibility to overlay structures—like converting an alphanumeric string into numeric sub-fields or handling variable record formats.

In my latest video, I break down:

-> Exactly how the REDEFINES syntax works

-> Crucial compiler rules you must follow (like handling level numbers and size limitations)

-> Practical, real-world project scenarios

If you want to sharpen your mainframe COBOL programming skills or need a quick refresher, check out the full tutorial here:

Watch the video on YouTube: https://www.youtube.com/watch?v=XbYteTi9d28


r/cobol • • 28d ago

Career in COBOL

31 Upvotes

I've been working as a Business Data Analyst for the past 2 years and 3 months, and before that, I spent nearly to 6 years as a Software Developer, specialising in VB.NET and SQL.

Throughout my career in SQL I've been involved in developing, maintaining and troubleshooting our nightly ELT process, using our bespoke ELT software and SQL Server. I'm comfortable working with existing codebases, investigating issues and maintaining business-critical systems.

Recently, I've become increasingly interested in COBOL and mainframe development, and I'm seriously considering pursuing it as the next step in my career.

However, I'm struggling to work out how to break into the industry. Most of the COBOL positions I've come across seem to require several years of commercial COBOL or mainframe experience, and there don't appear to be many junior opportunities available.

I'm based in the UK, and ideally I'd like to make the transition without having to start my career over again, particularly given my existing development experience.

I'd be interested to hear from anyone currently working with COBOL or IBM mainframes.

  • How did you get into the industry?

  • Would my previous software development and SQL experience be relevant to employers?

  • What would you recommend learning beyond COBOL itself, such as JCL, z/OS, Db2 or CICS?

  • Are there realistic routes into the industry for experienced developers who haven't worked with COBOL professionally?

  • Is it realistic to transition without taking a significant salary reduction?

I'm happy to dedicate time to studying and building my knowledge independently. I'm just unsure how to turn that into an actual career opportunity.

Any advice or experiences would be appreciated.


r/cobol • • Oct 15 '26

I tested LLM translations of COBOL to Python against GnuCOBOL on hidden inputs. Plain Python passed ~99% of the shown examples but only 82-91% of the hidden tests.

12 Upvotes

I've been building cobol-equiv, an open-source harness that checks whether a Python translation of a COBOL program behaves exactly like the original, using GnuCOBOL as the oracle. It comes with a small Python runtime for COBOL numeric semantics (PICTURE, COMP-3, ROUNDED, SIZE ERROR), validated against GnuCOBOL on 9,769 generated cases with 0 disagreements on 3.1.2.

Then I used it to measure LLM translations. 50 programs: 30 public ones (Rosetta Code and Open Mainframe Project examples) and 20 written for the repo. One model, 3 attempts per program, protocol fixed before any run. The translator saw the COBOL source and two example input/output pairs; scoring was on hidden inputs (generated plus PICTURE boundary values).

conditionshown exampleshidden tests (public / own programs)
C: plain Python, stdlib only98.9% / 100%91.1% / 81.7%
A: with the COBOL-semantics runtime98.9% / 98.3% (after fixing my bug, see below)
B: A plus up to 3 repair rounds with test diffs100% / 100%, all after one round

What broke the plain-Python translations was not logic, it was COBOL semantics:

  • ACCEPT into 9(5)V9(3) cuts the input to the receiver length, so the last decimal digit is dropped. The translation kept it.

  • An 11-character input into 9(10) loses a digit on the left.

  • A negative zero printed as "-0", where GnuCOBOL edits zero without a sign.

  • Non-numeric input converted differently.

The embarrassing part: the runtime I gave the model had a bug. CobDecimal compared objects by identity and had no ordering, so most failures in condition A (crashes and two infinite loops) were mine, not the model's. The pre-registered numbers stay primary in the repo, and a corrected sensitivity analysis is published next to them, with every verdict that flips listed.

Limits, plainly: small corpus, one model on one date, GnuCOBOL instead of an IBM compiler, attempts of the same program are not independent, and at program level the A vs C difference is not statistically significant.

Repo, protocol, raw prompts and replies, and the verifier: https://github.com/abdulazizbalu/cobol-equiv

I'd really value critique from people who work with COBOL: which semantic traps would you add, and if you have small, deterministic programs under a permissive license, I'd like to add them to the public track.


r/cobol • • Oct 06 '26

COBOL level 66 - RENAMES Clause

1 Upvotes

RENAMES Clause:

The COBOL RENAMES clause (level number 66) creates alternative logical groupings or overlapping views of existing data items within a record without changing physical storage.

Syntax:

66 data-name-1 RENAMES data-name-2 [THROUGH | THRU data-name-3]

* Must use the special level number 66.

* Must immediately follow the last data description entry of the logical record.

https://www.youtube.com/watch?v=GE_MEelNXeA


r/cobol • • Sep 28 '26

Our 1990s COBOL ERP only allowed 3 ODBC connections, so we taught Python to read its data files directly

29 Upvotes

TL;DR: Our ERP stores everything in AcuCOBOL Vision files. The only official way in was a 3-seat ODBC driver that was always maxed out and occasionally crashed. We reverse engineered the file format, now read the raw .dat files directly (read-only), and mirror 66 tables into Postgres every 5 minutes in about 35 seconds. It took a few weeks, one scary mistake, and a lot of verification.

The setup

We're a small food manufacturer running an ERP that's been around since the 90s. Under the hood it's AcuCOBOL, and every table is a Vision indexed file: a .dat with the records and a .vix with the index.

Everything modern we run (dashboards, EDI, order imports, a wholesale portal) reads a Postgres mirror of the ERP. That mirror used to be fed by a bridge over ODBC, through a vendor driver licensed at 3 concurrent seats. Those seats were spoken for all day by shipping stations and automation, the ODBC server is a single-threaded binary from 2014 that pegs one core, and a full refresh took hours. When it fell over, everything downstream went stale.

The idea

The files are just bytes on a share. If we could decode them ourselves, we wouldn't need a seat at all.

What made it possible: the ODBC product ships its own catalog describing every record layout. For each table it lists every field with its byte offset, length, PIC clause, usage, decimal places and date format. That's basically the COBOL copybooks in queryable form, so we never had to guess a field.

Cracking the file format

Vision files have a header area, then records stored in slots, each with a small header of its own. Where the records start, how big that per-record header is, and the stride between records all vary by file. So instead of hand-deriving 66 of them, we wrote a generator: try candidate layouts, decode a sample, and score how many decoded rows exactly match known-good rows pulled over ODBC. The winner goes into a config, and nothing gets in without validating against live data.

Making it safe to cut over

This is the part that actually took the time. We ran the reader in shadow for weeks next to the old bridge:

  • every night, a full row-hash comparison of every table, with both pipelines normalized the same way

  • every two hours during business hours, count checks and field-by-field spot checks on the busiest tables

  • a gate: 10 consecutive clean business-hours cycles on the order header file before we'd switch

  • the reader code and configs are hashed together, so any change resets the streak

What it looks like now

  • 66 tables re-checked every 5 minutes, about 35 seconds per sweep

  • each record's raw bytes are fingerprinted, and only rows that actually changed get written

  • files are opened read-only, and the reader never touches the ODBC service (4 small tables still ride the old path while we finish them)

  • a row only gets deleted after it's missing from the source on two consecutive sweeps, so one bad read can't wipe live data

Things that bit us

  • Live users lock records. Someone editing an order holds a byte-range lock on part of the file, and any read that hits it fails. We retry with backoff and treat a lock as "no data this pass," not an error. Once a desktop session died mid-edit and its server-side runtime held a lock for five and a half hours.

  • Files change under you. We check size and mtime before and after each read and retry if they moved.

  • REDEFINES. Two fields describing the same bytes, and the catalog's ordering of the tie isn't something you can derive.

  • "Last synced" changed meaning. The old bridge rewrote every row on every pass, so a timestamp meant "last checked." Ours only writes changes, so it means "last changed." Four freshness monitors started calling quiet tables dead, and all of them had to be repointed at the reader's own heartbeat.

  • Our own big mistake. During cleanup we deleted about 1.4M rows we believed were stale leftovers. We'd found them by comparing against the reader's output, but the reader deliberately skips very old records, so everything older than that cutoff looked "missing." It was real history. Every deleted row had been copied aside first, so it came back as archive tables. Lesson: an anti-join only tells you something is stale if both sides cover the same key range.

  • Bloat. The old bridge rewriting every row every 15 minutes for months left some Postgres tables 7x their real size. One night of compaction took the database from 45 GB to 32 GB.

How it got built

Full disclosure: most of the reverse engineering and code was done pair-programming with Claude. It was great at grinding through byte offsets and writing verification harnesses. It was also the one that made the delete mistake, and the one that dug it back out, which honestly felt about right for a pair programmer.

Happy to answer questions if anyone else is stuck feeding a COBOL system through an ODBC straw.


r/cobol • • Sep 28 '26

Any Tandem / HPE Nonstop COBOL Developers out there?

10 Upvotes

Looking for advice, maybe even. short term engagement for one of two experienced Nonstop COBOL developers. I won't lie, right now our opportunity is quite wide and I'm open to ideas, but there may also be scope to build a fairly recurring bit of work. Anyone interested in discussing please reach out. Coming from a HPE Nonstop company working with Customers all round the world.


r/cobol • • Sep 27 '26

Looking for Mainframe opportunities in Europe

7 Upvotes

Hello people. Posting for any Mainframe opportunities in Europe for myself.

My background: I have 15+ years of industry experience working on Mainframes. Mostly my roles have been around 8 years experience in Development. Remaining close to 5 years in Production support - L2/L3 Oncall etc. I was also part of migration of DB2 z/OS to LUW.

I have worked for multiple clients, projects, geographies from diverse backgrounds. Banking, Insurance, Manufacturing, Utilities are the areas I mainly worked in Dev/Production support. Currently I am supporting a Mortgage application for a Large Danish bank. I can adapt to any domain/projects easily and I am sincere at my work.

I am currently based out of India and looking for opportunities to work at onsite in Europe for long-term (preferably Nordics but not necessary). If you have a role within your teams or know a position where I can fit, please DM me. I can share my CV/CL/LinkedIn etc. for interview and we can take it from there. Would be grateful for any help. Thank you for the read.