Overview
Skills
Job Details
Job Title: Mainframe Systems Programmer – MQ Specialist
Location: Columbia, SC (Partial Onsite; Remote Possible with Approval)
Pay Rate: $60/hour
Schedule: Monday–Friday, 8:00 AM–4:30 PM (OT/on-call/weekends as needed once trained)
Work Authorization: USC only
Job Summary:
We are seeking an experienced IT professional with strong mainframe systems programming skills, specifically in IBM MQ on z/OS. This role will support the maintenance and configuration of MQ infrastructure, handling test and production issues, fulfilling customer requests, and contributing to projects like MQ upgrades and configurations. The ideal candidate is a hands-on MQ administrator—not just a user—who is comfortable managing queue managers, queues, and troubleshooting real-time issues in a dynamic mainframe environment.
Key Responsibilities:
-
Resolve test and production issues related to MQ
-
Fulfill customer requests: create/modify queues, queue managers, adjust queue depths
-
Participate in MQ infrastructure projects (e.g., installs, upgrades, server configurations)
-
Perform internal monitoring and address error reports
-
Handle multiple tasks and priorities in a fast-paced environment
Required Qualifications:
-
Bachelor’s in Computer Science, Information Systems, or related field; OR equivalent work experience (6 years total; at least 2 in systems programming with MQ)
-
6+ years of IT experience, with extensive mainframe systems programming background
-
Strong expertise in:
-
IBM z/OS MQ (mainframe)
-
JCL
-
Creating and maintaining queue managers/queues
-
Nice to Have:
-
Experience with CICS, IBM WebSphere MQ, COBOL, Unix, or zLinux
-
Familiarity with MQ version 9.3 is a plus
Work Environment:
-
Partial onsite (Tues–Thurs mandatory); Remote may be considered but is not guaranteed
-
Must be open to working after-hours/on-call once fully trained
Important Note:
This is not a user-facing MQ role. We’re looking for a backend MQ administrator/programmer who understands the technical configurations and internals—not just how MQ functions from a user standpoint.
#INDREM