3rd Shift AS400/ Mainframe Operational Support
Mainframe Operational Support
Location: Brown Deer, WI
Shift: Tuesday – Saturday 11PM – 7AM
Key skills: Mainframe, JCL Coding, Control-M batch processing
- Responsible for technical support including: monitoring the company’s ticketing system while addressing issues as they come in via phone, email, chat, etc.
- Support current mainframe architecture using Control-M & JCL. The specialist will monitor tickets, determine scope and severity of issues, research and analyze resolutions and/or workarounds, troubleshoot issues to determine root cause, and escalate to other areas of the business.
- In the absence of the problem and incident management team, be able to step in as the problem or incident manager and perform all duties of that role
- Work with mainframe systems; Control-M, as well as JCL and monitoring the production batch environment, create knowledge based articles of everything we are currently using the mainframe for
- Train and Mentor the Level 1 and Level 2 staff on troubleshooting systems and methods, particular to the store and corporate network. Ensure a complete knowledge transfer and succession plan document is created for each individual
- Leveraging existing monitoring tools, for both store and corporate networks, develop reporting involving, but not limited to network performance monitoring, NetFlow traffic analysis, packet captures, SNMP, etc…
- Create thresholds in existing monitoring tools to be utilized for alerting purposes, create topology maps, and performance metrics to be published to IT Infrastructure using a productivity tool such as SharePoint
- Work with Level 2 regarding the mainframe production batch environment trends and discrepancies, and on a regular basis, revisit SLAs with the business to ensure accuracy and trends
- Utilizing the current ticketing system, to not only create, modify, and resolve tickets, and work with both the internal Infrastructure team and Stores regarding trending analysis.
- Develop proposal twice per year on pro-active measures we can take to mitigate ticket volume, example: self-service utilizing the ticketing system’s Knowledge Base