SUMMARY

• I am submitting my resume in consideration for the Mainframe Developer opportunity in Confidential .
• My skill set is usually a good fit for many IBM mainframe programming jobs.
• I am currently seeking a long - term opportunity. The longer the better Many employees were recently laid-off by Confidential
• I am an experienced mainframe programmer analyst, who is articulate, and demonstrates a high degree of initiative.
• If the client is interested, I will gladly grab a flight to Denver for an in-person interview.
• And will relocate if we are a match. Any salary above $80K is fine with me. My last salary was $85K.
• Once earned $95K plus an annual bonus.

PROFESSIONAL EXPERIENCE:

Sr. Mainframe Programmer Analyst

Confidential

• As a Sr. Programmer Analyst, this candidate typically wears many hats every day. But generally, he scans and analyzes over 1,800 Cobol and IBM Assembler programs to locate the impacted modules for a new project. After developing a technical solution for the requested enhancements, the candidate writes a DESIGN specifications document.
• The DESIGN specifications document includes these items as a minimum: new program descriptions, old program changes, copybook changes, new copybooks, JCL changes, control card changes, SORT changes, CICS screen/map changes, DB2/SQL changes, file conversion descriptions, all REPORT changes, and TEST CASE scenarios. This document serves as a blue print for the subsequent coding activity.
• Eventually, the candidate codes the IBM Assembler program changes. He usually mentors the junior level Cobol programmers with the Cobol code changes. Provides them direction on good coding techniques, assists with their program debugging issues, and serves as their primary technical resource person.
• The First Data legacy mainframe environment is mainly a combination of COBOL II, IBM Assembler code, and CICS. Very large volumes of BATCH and ONLINE transactions are processed daily. The main file system is VSAM. But the environment was upgraded with DB2 around year 2000. The DB2 database for the candidate’s team is comprised of 27 tables. And uses version 10.
• The technical environment also includes COBOL II, IBM Assembler, CICS, JCL, VSAM, DB2, SQL, TSO/ISPF, Endevor, Intertest, and the IBM z/OS mainframe.

Sr. IBM Assembler / CICS Programmer

Confidential

• The candidate performed IBM Assembler and Cobol code development on an IBM legacy mainframe life insurance system. Code research and analysis, technical design, coding, and project testing were entirely his responsibility for each project. His responsibilities also included Online CICS coding, and BATCH cycle support. Additionally, the candidate was the team’s subject matter expert.
• He was the primary contact for trouble shooting all production issues. Provided hands-on production support for the daily BACTH cycle. Typical activities were debugging program ABENDS, creating file fixes, and preparing JOB restarts.
• The Torchmark technical environment contained COBOL II, VSAM, JCL, Online CICS, BIM, Cobol, IBM Assembler, and Abend-Aid on an IBM mainframe.

COBOL Mainframe Programmer

Confidential

• The candidate performed routine IBM mainframe COBOL development on a Warehouse Management System. Code research and analysis, technical design, coding, and code debugging were his main responsibilities. The programming languages were CICS and Cobol. The file systems were VSAM and DB2. Both batch and online transactions were processed. The projects were usually 3 to 6 months in duration.
• The TTI technical environment included JCL, VSAM, DB2, SQL, Cobol, CICS, TSO/ISPF and File-aid, on an IBM mainframe.

IBM Mainframe Programmer

Confidential

• The candidate performed as a programmer analyst for several legacy mainframe systems in the credit card industry. COBOL, CICS, and IBM assembler were the programming languages. On-call duty was the usual activities: debugging program ABENDS, and preparing cycle restarts.
• The MBNA environment used DB2 tables quite heavily. CICS, Cobol, SQL, and SPUFI were a primary focus. The programmers worked very closely with the DBA’s. That collaboration enhanced our DB2 skills immensely. As an example, the MBNA programming staff created DB2 test tables by using QMF and SPUFI in combination.
• All projects were managed by a very rigorous SDLC methodology. Code reviews and team walk-thru’s were plentiful. The MBNA technical environment was very robust and included: Endevor, Abend-aid, File-aid, TSO/ISPF, Syncsort, JCL, COBOL II, IBM Assembler, QMF, SPUFI, SQL, TSO/ISPF, CICS, VSAM, and DB2 on an IBM z/OS mainframe.

IBM Assembler Programmer

Confidential

• The candidate performed mainframe code development on a legacy life insurance system, both Batch and Online. Code analysis, design, coding, and project testing were all his responsibility for every project. The USLIFE application systems were a combination of COBOL and IBM Assembler code. The technical environment was the usual mix: JCL, TSO/ISPF, CICS, Intertest, VSAM, File-Aid, PROCs, Syncsort, and MVS on an IBM mainframe.
• DB2 was migrated into the USLIFE environment in the mid 1990’s. All programmers received in-house training on DB2 and SQL. The DB2 classes were very thorough, and even explained the functional relationship between DB2 and VSAM. These classes were the candidate’s very first exposure to DB2. Considering he was already an expert with VSAM, the transition to DB2 was much easier for him than for others.