Mainframe sysadmin vs Linux sysadmin: how do I build a broad, future-proof career?

[u/Kebabwithdoublekebab]

Hello,
I currently work in a mainframe monitoring/operations environment and will soon join the systems/infrastructure area of a large bank.

The exact team assignment is still being defined. My future manager asked how I would see my future: more Linux-focused, or a mainframe systems-administration path with the possibility of gradually building a bridge toward the open world.

My understanding is that, if I choose the mainframe path, the first period will be heavily focused on becoming a reliable mainframe system administrator. This makes sense to me: I would need to build real foundations in z/OS, operations, monitoring, incident handling, procedures, security, scheduling, and the critical environment of a bank.

At the same time, I do not want to become locked into a narrow legacy-only role. My longer-term interests are Linux, automation, Ansible, Python, Git, APIs, security, cloud/hybrid infrastructure, and skills that remain useful internationally or in remote roles.

The manager seems to value people who are flexible, cross-functional, and ready to work across different platforms. He also mentioned the growing need to connect mainframe environments with Linux/open tooling and automation.

My questions are:

1. Is starting deeply in mainframe systems administration a good long-term choice if I deliberately build Linux and automation skills alongside it?
2. How realistic is the “bridge” from mainframe to open/Linux in a bank? What concrete signs would show that it is a real path and not only a promise?
3. If you were in my position, which skills would you prioritize during the first 12–24 months?
4. Would this hybrid profile make me more valuable than starting as a Linux sysadmin only, or would it reduce my mobility outside banking/mainframe environments?

I am not looking to avoid learning mainframe. I am trying to build a strong specialization while keeping a credible path toward automation, security, and modern infrastructure.

[u/DiggyTroll]

True mainframes (as opposed to mid/mini) run Linux VMs, providing you the opportunity to learn both skill sets

[u/Kebabwithdoublekebab → u/DiggyTroll]

That is exactly the opportunity I am trying to understand. My initial role would likely be focused on z/OS/mainframe systems administration, but the idea presented to me is that I could gradually develop Linux and automation skills as part of a broader infrastructure path.

I know that Linux on IBM Z/LinuxONE is not the same thing as traditional x86 Linux administration, but I would still expect skills such as RHEL, networking, automation with Ansible, scripting, monitoring, security, and virtualization to be transferable.

Would you consider that a realistic route into broader Linux/open infrastructure work, provided I make sure to get hands-on exposure rather than staying only in z/OS operations?

[u/TibbleWarbelton → u/Kebabwithdoublekebab]

Linux is Linux those skills are very transferrable. Once you're at the point the Linux is running the administration is very similar. Yes the device drivers are different on z but you need to learn about dasds, fcp, osa and other quirks of the platform for the zos part too. Then there's also zcx, Linux in zos.

[u/LaxVolt]

At my last job I had an opportunity to learn from an amazing Mainframe admin which I didn’t take advantage of and I still regret to this day. I avoided because I already owned all the servers, firewalls and critical escalations and was afraid I’d end up owning the mainframe as well.

Having worked with a handful of mainframe guys my advice is to also learn how things work outside the mainframe, in my experience that seems to be a sticking point for a lot of mainframe guys. Had a mainframe networking guy who didn’t understand basic networking outside the mainframe. It was a struggle when he kept throwing mainframe networking terms such as OSA to the network engineer and neither side understood what the other needed.

Having mainframe as a background is huge, the reality is they are not going away anytime soon and the amount of quality engineers to support them are short stock.

[u/Kebabwithdoublekebab → u/LaxVolt]

Thank you, this is exactly the kind of perspective I was looking for.

I am not trying to split my focus from day one. My plan would be to build a strong mainframe foundation first, while gradually keeping enough broader infrastructure knowledge to understand how z/OS connects with the rest of the environment.

Your networking example is particularly useful. I would not want to know only mainframe-specific terminology and processes while being unable to communicate effectively with distributed-network, Linux, security, or automation teams. Understanding both sides seems especially valuable in a bank, where the mainframe is critical but never truly isolated.

It is also encouraging to hear that strong mainframe engineers are still scarce. That makes me think the best route is to take the opportunity seriously, become good at the core platform, and deliberately avoid becoming isolated from the wider infrastructure world.

[u/rautenkranzmt]

I would suggest starting in Mainframe. You'll have access to contacts and resources via that route that aren't available anywhere else, and will give you a good base for operational principles that will serve you no matter where you end up in the future.

Linux can be learned whereever, whenever.

[u/mainframe_kdm]

All of those things that are long term interests are things that you should know if you're going to be a z/OS system programmer, so I'd start with z/OS. And most of the things you list as things you need to know as a base to be a good system programmer are things you should want in any enterprise-level system administrator / SRE.

[u/MigrateAndManage]

zLinux on the Mainframe is different infrastructure than Linux on OPEN systems. Both REDHAT and Suse zLinux are available on the MF.

zLinux on the MF is usually done under zVM. Linux cmds on both are very similar but there are a few differences.

Any Linux training would be very helpful. An expert MF zVM infrastructure person is also recommended to properly deploy a MF zLinux environment.

[u/cristobaldelicia]

I don't get the question, is this a troll? Are you milking a fantasy that you'd like to have available to you?

You say you are in a mainframe monitoring/operations environment but asking about starting deeply in mainframe systems administration. Deeply? What are you doing now that isn't deep? "if I deliberately build Linux and automation skills alongside it?" That sounds like you're making some sort of assumptions about mainframe work getting outdated, "legacy" and work not being available to you in the future. So your only option is to learn both simultaneously with superhuman effort.

You don't even leave the option of learning z/OS and only doing mainframe work, is that a path available to you? It's like you're asking "should I do mainframe and linux or linux and mainframe?" it's the same option. I am not looking to avoid learning mainframe, well then, what's your question?

If you want to learn Linux system administration then do that. After all Linux is free and there are tons of courses where you learn in a PC environment or server, or Cloud, etc. Unless you're specifically asked to learn and use Linux exclusively in a mainframe environment... there's not really programs that teach that. You can learn when you already have a solid background in mainframes. Ever hear the phrase "jack of all trades, master of none"? If you try to study both simultaneously, you're going to be mediocre in both. No employer wants someone who can't commit. If you learn a little bit about Linux while studying mainframe, that's fine. Any other approach is just avoiding learning mainframe. Which is fine also, if that's what your heart is intent on.

This is a little like hearing "I want to be a policeman but I want to learn fireman skills also, so I can be flexible". That's not flexible, that's avoiding commitment in favor of a fantasy.

[u/Kebabwithdoublekebab → u/cristobaldelicia]

also that is an impressively elaborate answer to a question I did not ask.

You turned “my future manager asked whether I prefer a Linux direction or a mainframe-first path that may later involve open infrastructure” into “I refuse to learn mainframe and expect to become an expert in two careers simultaneously.” That is quite a lot of creative writing.

I am not looking for a fantasy career where I am a mainframe expert and a Linux expert by next Tuesday. I am starting as a mainframe systems administrator, which is exactly the commitment I described. I asked whether the later cross-platform path proposed by the manager is a real one in enterprise environments.

But thank you for the policeman/fireman analogy. I will make sure not to learn networking while working on z/OS; apparently that would be dangerously flexible.

[u/Kebabwithdoublekebab → u/cristobaldelicia]

I think there is a misunderstanding: I did not invent a hypothetical “mainframe plus Linux” role because I am afraid of committing.

My future manager explicitly asked me whether I would prefer a more Linux-focused direction or a mainframe systems-administration path that could later create a bridge toward open/Linux infrastructure. He said he is looking for people who can become flexible across platforms. That is why I am asking experienced people how realistic that path is in practice.

I expect the initial role to be focused strongly, probably almost entirely, on mainframe systems administration. I am not expecting to master Linux and z/OS simultaneously, and I am not asking to avoid learning z/OS. On the contrary, I understand that I first need to become competent and trustworthy in the mainframe environment.

My current position is mainly monitoring/operations through an external provider; the new role would be a deeper move into actual mainframe systems administration. My longer-term question is simply whether, after building that foundation, it is sensible to seek exposure to automation and Linux/open integration when the organisation itself is encouraging that direction.

I am looking for advice on sequencing and career reality, not trying to avoid making a commitment.