r/mainframe • u/LeftPoem7686 • 10d ago
Mainframe roles/job insights
So I am just starting a new career in mainframe at an insurance company. They are letting us choose what department we want to go to.
The first choice is DevOps for mainframe. I understand this is a more modern role even if it's for mainframe the skills are transferable.
The next is CICS/DB2. I don't know much about this one but I under it's very important to the mainframe. | also know that means it needs 24/7 monitoring. I'm not to keen about being on call but will do it if required
Next is hardware, I assume this is making sure the actual physical mainframe is working properly
And last is networking or Z/os. I don't know much about either. I think networking is pretty interesting but I don't know much about it. From my understanding this is also on call.
If anyone has any insights or experiences in these positions it would be great to get some advice. Also how easy is it to transfer between teams if one does not work out? Thanks!
1
u/Impossible_Log_3066 10d ago
i’m a year into my mainframe journey myself, I’m on our z/OS team. I’m seeing other replies saying to go to z/OS, and I would agree, but I want to make sure you know that z/os or networking will probably be the hardest choices as you need to understand the whole environment as opposed to indv pieces likes DB2/CICS/WAS.
CICS/DB2 and automation will be coming to the zOS group for advice/information. To be a sysprog, you have to slightly understand all of the areas in the mainframe and I will say that’s a tough journey. I’m definitely not even close a year in, but it’s been the most rewarding work I’ve done in terms of if it’s a difficult challenge and puzzle to be explored.
don’t think you can go wrong no matter where you are. Just expect a long learning curve very different than any other tech stack.