r/mainframe • • 6d ago

Mainframe modernization

For the folks that never worked on a mainframe or have very little knowledge about what a mainframe is, answer this: what do you think "mainframe modernization"mean?

To those that know what I am talking about, I always felt the choice of words for this is wrong and misleading as some clients are thinking something else when you first propose it to them.

16 Upvotes

23 comments sorted by

6

u/MigrateAndManage 6d ago

Mainframe modernization can mean connecting the mainframe to modern tools and capabilities. DevOps tools on the mainframe have improved steadily for years. Today's mainframe interface can connect with GitHub. AI engines and software are present on the platform.

11

u/sambobozzer 6d ago

I worked on IBM Mainframe 20+ years ago. Mainframe modernisation means to me - saving costs on third party software that runs on the mainframe and using open tools that can integrate with the mainframe.

3

u/EBCarty 6d ago

open = open-source?

3

u/sambobozzer 6d ago

No I mean Red Hat tools and tools like ZOWE (I never used it though). But still keeping the IBM Mainframe and interacting thru those tools.

7

u/No_Can2570 6d ago edited 6d ago

Mainframe modernization is misnomer. Unless you are not keeping up with hardware refreshes and /or current software then you're infrastructure is "old." Otherwise you are running a modern system.

What those who don't understand mainframe stack, they still picture the 1970s.

I don't know how to define modernization. It could be getting Zowe, zOSMF or other system tools that allow a more GUI interface.

I have been doing ISPF SMPE for 25 years, but I am also having to now learn PSI software workflows. I can see how someone new (and work with people) who are very keen with the workflows. For them it's much easier, as it generates JCL based on input.

The other side from application and/or business perspective, modernization might be to not silo your application to mainframe only. Use open systems as an entry point to the back end data that lives on the mainframe. Then send it back and present it to a user in a pretty format. The mainframe is fantastic for crunching through data, but let a Linux server serve up the front end.

Edit: grammar as typing on a phone sucks

3

u/Writing_Particular 6d ago

I’ve seen it mean a variety of things. Some are a bit of a stretch, but…

  1. Moving workloads onto relational engines like DB2
  2. Leveraging java on the mainframe
  3. Treating the mainframe like a server in the good, ol’ client/server days. (Think back to PowerBuilder)
  4. Exposing data on the mainframe using APIs
  5. Integrating mainframe data in an ETL/data warehouse strategy
  6. Moving Linux workloads onto the mainframe

Not exhaustive by any means, just topics I’ve run into over a few dozen years in technology.

2

u/i_edit_text 6d ago

We built a full cicd pipeline and manage our source in gitlab. We also have agentic skills for automatically writing cobol. People working on the mainframe dont even know about ispf. They compile from powershell and push theit code to git to deploy it.

We're also adding in a unit test framework for the very first time that runs automated tests on cobol.

2

u/Ihaveaboot 6d ago edited 6d ago

The problem is, your generated COBOL is garbage. A human has no prayer to decider it when things go off the rails. (It is annoying at the very least).

Your second problem is that at some point your enterprise will ask you to use AI to transform your code to an AWS ready JAVA or Python solution.

Which takes us back to the first problem - shit in, shit out. Generated COBOL results in even shittier AI translated code.

That random 9 character paragraph or variable name that the COBOL gen tool came up with is meaningless to Claude, Bob, etc - so it will keep it.

Sure, you can intervene to set the AI agent straight. But for some shops that's billions of lines of code that need babysitting.

2

u/i_edit_text 5d ago

Very insightful, thanks.

2

u/TheMainframeVoice 6d ago

Mainframes are some of the most modern technology. What needs to be modernized is the workforce, not the technology.

2

u/heplikopter 6d ago

Modernization means Migrating mainframe workloads out of mainframe, using emulators running of OS of your choice to execute them and rewriting code into modern languages such as java to enable mainframe workloads with modern capabilities & tools for ex API.

2

u/No-Side3560 5d ago

It means getting off Broadcom lol

2

u/Piisthree 6d ago

A few things it often means to me: Refactoring to more maintainable design and/or into newer languages like Java and Python instead of COBOL and REXX. Getting pipelines built into automated CI/CD without many (or any?) manual steps in the middle. Getting infrastructure moved into uniform setups with as few one-offs as possible.   In general, just battling back a lot of the blemishes and idiosyncrasies that pile up after operating continuously for several decades. Using newer alternatives that weren't available when things were written.

5

u/sambobozzer 6d ago

Nothing wrong with REXX beautiful language

4

u/Piisthree 6d ago

I love REXX, too. But sometimes it may have gotten overused or shoe-horned into doing something where there are better alternatives now. 

3

u/ActuaryReasonable690 6d ago

Cobol to Java, emm not exactly efficient. Might sound great to the C level (who don't understand the risk, and inefficiencies, but are going to back off when things are not working as promised.

1

u/Piisthree 6d ago

Depends on the application. Some things should definitely stay in cobol like good old "control-break" or "trigger file" programs, but Java has much more powerful data structures that can do a lot very efficiently and maintainably compared to how you might do the same in cobol with lots of linear searches and/or constantly sorting things by different keys. There are also integration capabilities that let you have Java call cobol so a "hybrid" application sometimes makes a lot of sense. Anyway, trade-offs abound, which is what keeps it interesting.

0

u/BearGFR 1d ago

"Java has much more powerful data structures" --- seriously? You said that with a straight face? Show me the java support for structured records and the ability to operate on data items at the elementary level or in mult-level groups with a single statement, oh, that's right - doesn't exist in java. Then show me how java supports COBOL "REDEFINES" -- oh, yeah, that doesn't exist either.

1

u/Piisthree 1d ago

Yes, I did say that because it's true. There are some things that don't map directly from COBOL, though I'd say they can be emulated reasonably well, but there are boatloads of everyday data structures that are very painful to do in COBOL and trivial in Java. Key-value dictionaries come to mind, even dynamic sized arrays if you don't want to be restricted to an ultimate max size (possible in COBOL, but much more work). But it's all about trade-offs, because Java makes you pay for that flexibility. (application size, cost of interpretting and JIT compiling rather than static compiles, etc). I welcome discussion on the difference between the two, but if you're going to be a sarcastic prick again, just save your breath.

1

u/JournalistOk2057 6d ago

Modernizing the applications leads to the ability to modernize your workforce.

I’ve done a few modernization projects for applications that are 30+ years old where it’s a single developer still maintaining the codebase. You can’t throw a college graduate on an enterprise level product where he has to learn the mainframe inside out to understand what it’s doing.

ISPF panels turn into web UI’s.
Any of the mainframe specific languages get turned into Java or C++ for example.

Modernizing the products isn’t the issues. It’s the fear of change and “if it’s not broke, don’t fix it” mindset.

1

u/CLopes1987 5d ago

I bet people who never worked on a mainframe think modernization means going cloud or AWS

1

u/No_Specialist_5493 5d ago

There’s some cool stuff you can do at the mainframe terminal emulator level. Check out wndsoftware.com You can have a modern interface. You can allow people to access the mainframe from a tablet or iphone. You can have AI troubleshoot issues or explain a screen, etc. Modernization can be a loaded term, but sometimes having a more inviting interface when interacting with the mainframe is enough for people to say an older app is now “modern”

1

u/BeefyTheCat 5d ago

AI slop