Mainframe MQ System Programmer
Kyndryl (company site, opens in a new tab)6+ yrsChennaiOn-siteDirect career pageEst. 12–20 LPA
Posted 5h ago
Reach people at Kyndryl
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Kyndryl you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own installation, implementation, upgrades, configuration and ongoing maintenance of a large IBM MQ environment on z/OS.
- Maintain MQ performance and availability through system-option management, queue-manager tuning and troubleshooting.
- Support disaster-recovery planning and execution across data centers, and provide primary or backup on-call coverage during nights and weekends.
Minimum Requirements
- Work Experience Required: 6+ years as a Mainframe MQ System Programmer.
- Expertise installing and upgrading MQ for z/OS using ShopzSeries and SMP/E; ability to install, configure and maintain WMQ and associated system software.
- Strong MQ troubleshooting using command-line and monitoring tools; experience with MQ Explorer, Tivoli, Omegamon, SYSVIEW, BMC MainView, MQATTACH or ICC. Familiarity with MQ clustering and distributed integration is also listed.
- Support for extended-hours on-call rotations, including nights and weekends.
Ideal Candidate Profile
- Has hands-on experience administering mainframe MQ objects and managing queue managers, tuning and production performance.
- Is suited to mission-critical operations requiring disaster-recovery readiness and support across data centers.
- A bachelor’s degree in computer science or a related field is preferred; automation scripting with REXX or similar is also a preferred signal.