Client note:Remote (Candidate must be local to Denver, CO)
Job Summary:
nvestigate and document mainframe processes/applications sufficiently to migrate the workload to alternative architecture or decommission the processes.
Responsibilities:
- Collaborating with OIT resources build documentation templates for the decommissioning and migration effort.
- Collaborate with OIT and business resources investigating these mainframe processes determining whether they need to be decommissioned or migrated to alternative technology.
- Review existing documentation
- Research mainframe JCL, procs, source code to determine the requirements for migrating these processes off the mainframe or decommissioning these processes
- Identify active mainframe workload.
- Document those processes sufficiently that need to be migrated off the mainframe to alternative technology.
- Document those processes sufficiently that need to be decommissioned.
- Use of enterprise reporting tools to track and report progress and status.
- Potentially assist in writing RFP
Deliverables (not limited to):
- Documentation Template(s), approved by the Project Lead
- Migration
- Decommissioning
- Meeting artifacts
- System documentation for required migration activities meeting the requirements identified in the Problem Statement
- System documentation for decommissioning activities meeting the requirements identified in the Problem Statement
- Creation of User Stories, Product Backlog Items with articulated Acceptance Criteria
- For data files and elements, establishing data dictionary and definition of all data transformation rules
- Weekly Project Status reports
- Project schedule
- Other project documentation as required
Required Skill Set:
- Mainframe knowledge (*must have knowledge)
- COBOL*
- CICS
- VSAM*
- JCL*
- CA 7 Scheduling Module*
- TSO
- Experience in various mainframe utilities to be able to complete the required documentation. Knowledge of Proclib and other mainframe utilities
- Excellent writing skills
- Analytical mind set
- Ability to lead in a matrixed environment.
The role of the Legacy Systems Specialist is to provide a variety of services related to support of systems and technologies that are no longer considered state-of-the-art or that require subject matter expertise that is no longer readily available due to the age and changes in system operations and functions over time. Legacy systems, while often characterized as those using older software, hardware, and network technologies, are also still providing mission critical support vital to many agencies. As such, Legacy System repair, maintenance, enhancement, and retirement require highly skilled and hard-to-find expertise.
- Provides planning & design assistance for the interfacing or data exchange with other agency system or technologies.
- Provide planning & design assistance and recommendations for the migration and conversion of legacy functions and data to new software, hardware, or computing platform environments.
- Develop, modify, test, and update existing Legacy systems. This includes producing design, test, and user documentation as required, and interfacing with agency staff and/or other contractors in a collaborative manner.
- Program, code, load, install, backup, repair, debug, reverse engineer, document, test, advise, cross train, and present as needed.
- Execute Legacy System conversion plans and activities required of such plans, such as, allowing for parallel operations, failsafe, rollback, and roll forward strategies as needed.
- Provide mentoring, training, ad coaching to IT project teams as required.
- Work directly with agency staff, as well as vendors and, when necessary, other state agencies in fulfilling and carrying out the requirements of assigned Legacy Systems projects.
- Where documentation isn't available, reverse engineer programs, functions, and system architectures, so as to reveal the source operation and document the I/O, data structures, and sequencing of operations within a Legacy environment.
Provide emergency Legacy System support during system failures or when critical deadlines appear.
5-10 years of experience. Generally commercial systems with minimal certification requirements.
| Type | | Category | | Qualification | | Description | | Competency | | Required | | |
| Skills | | Languages | | COBOL | | | | Novice (1-3 Years) | | No | | |
| Skills | | Others | | Communication skills both verbal and written | | | | Proficient (4-6 Years) | | No | | |