SUMMARY:

SENIOR APPLICATION DEVELOPMENT SPECIALIST with extensive experience in the analysis, design, and development of computer systems. Developed and implemented numerous full life - cycle software development projects as team lead, system architect, developer, analyst and full time consultant.

TECHNICAL SKILLS:

HARDWARE: IBM 3090, IBM 3080, IBM 3050, IBM 3030, IBM 360

OPERATING SYSTEMS: IBM/390, IBM ESA, IBM XA, IBM/360, Confidential, TSO/ISPF VM/CMS, Z/OS

PROGRAMMING LANGUAGES: FOCUS, RAMIS, COBOL, COBOL II, proCOBOL, TSO/CLISTEASYTRIEVE PLUS, STORED PROCEDURES.

DATA BASE: Confidential, BMS, VSAM, IDCAMS, DB2, SQL, QMF, SPUFI, IMSISAM

UTILTIES/TOOLS: ENDEAVOR, XPEDITER, FILEAID, SYNCSORT, Control-MJCL, SMS, all IBM Utilities

PROFESSIONAL EXPERIENCE:

Senior Programmer Analyst, MD

Confidential

Responsibilities:

• Working for KSI at Social Security Administration, I monitored Confidential ’s space allocations within their mainframe logical partitions ( Confidential ) and took necessary steps when space problems arose.
• Modified all of Confidential ’s Stored Procedures involved with ‘ Confidential ’ system.
• Produced ‘Day Before’ Confidential system for Check free to sell to its bank customers.
• Managed all Confidential ’s programmers and activities involved with Confidential ’s Confidential system.
• Developed system for Confidential to monitor sales versus competitor Solocup.
• Supported all data processing activities at Confidential in Columbia MD.

Confidential, Woodlawn, MD

Senior Programmer Analyst

Responsibilities:

• I determined what volumes were available within that partition and incorporated them into the pool of processing disk volumes for that Confidential and that increase in Confidential space, prevented space abnormal endings.
• Before working on this contract, I became proficient in Systems Managed Storage (SMS) and all the necessary procedures needed to identify the mainframe disk storage threshold.
• Nightly, I addressed any production job failures, taking necessary resolution steps as dictated by Control-M for the abnormal situation.
• Control-M instructions were followed to the letter, nightly at Confidential .
• Used COBOL/COBOLII, Z/OS, VSAM, DB2, SPUFI/SQL, Control-M, TSO/CLISTS all IBM utilities.

Confidential, Bethesda, MD

Senior Programmer Analyst

Responsibilities:

• Modified all Stored Procedures involved with Confidential ’s ‘ Confidential ’ System so that all Stored Procedures were using projected numbers rather then actual numbers in regard to displaying ‘Group’, ‘ Transient’ and ‘Reserved’ room totals on corporate reports and entry screens.
• Responsible for modifying the COBOL and SQL code involved with the DB2 database extractions so that the starting date range of the extractions, were one day earlier than actual day being processed. This caused projections to be used rather than actual numbers.
• Users wanted projected totals, rather than incomplete and inaccurate actual totals which were not accurate until the next day.

Confidential, Baltimore, MD

Senior Programmer Analyst

Responsibilities:

• Assisted with creation and implementation of new application to be sold to banks across the country.
• I was responsible for writing all Programs (Cobol-II) and Confidential screens involved.
• This application will allow banks to have all checks issued, to be processed in a ‘Day Before’ Scenario, so that any errors associated with the checks can be caught and corrected before the actual DDA processing takes place at midnight each night.
• The system involved, allowed the individual bank’s users to enter through Confidential screens all the pertinent information from their checks. That information being: Date, Amount, Check Number, Route Transit Number and to whom the check was written.
• The Cobol-II program involved, which sent the Confidential screens to the terminals, took these inputted values and wrote them to a VSAM output file.
• I wrote a second program which would take a copy of the nightly DDA file, which is available to banks at 10:00 A.M., and compare it to the VSAM file which holds all the check information. If the checks from the DDA file agreed with bank entered VSAM values the entry was deleted from the VSAM file. If there were any differences both values from the DDA and VSAM file were written to an exception file so banks could investigate and resolve the differences before their nightly runs.
• By comparing, all typographical and Micro-feed errors were caught and the system was also able to prevent fraud by making sure the amount of a check being cashed is the actual amount of the check being written and that the person to whom the check was written was actually the person cashing it.
• As stated above, this system was sold to banks throughout the country.

Confidential, Owings Mills, MD

Work Order Manager

Responsibilities:

• Responsible for the ‘ Confidential ’ system for the Social Security Administration
• Was responsible for all Lockheed programmers involved to ensure they were performing to specifications and that all avenues were covered with new modifications to COBOL programs for their annual release.
• I was also involved with all the coding and file extractions: COBOL, DB2, VSAM, JCL, and TSO/CLISTS.

Confidential, Baltimore, MD

Senior Programmer Analyst

Responsibilities:

• Assisted Confidential in its migration to new owner, SOLO CUP.
• Developed system to monitor sales from SOLO and Confidential to same customer base.
• This system used Cobol II for DB2 and VSAM extracts and ‘ Confidential ’ for report production.
• My past Mainframe experience was called upon daily to assist other groups as needed.

Confidential, Columbia, MD

Senior Programmer Analyst

Responsibilities:

• Provided support for all Data Processing activities for Marketing Group. Was responsible for analysis to guarantee all sales campaigns were successful through proper potential customer selection.
• Used Cobol II programs for customer extractions from IMS database or DB2 tables.
• I was only programmer on site and was responsible for creating and maintaining monthly master files of existing and potential Confidential clients.
• Produced DB2 or IMS extracts for any one of six marketing group team members to help with their daily analysis. Developed FOCUS reports to show which product was enjoying the most public support so radio and television commercials were aimed to the correct market.
• Developed TSO/CLISTs, for use by entire marketing group, so extractions could be scheduled and any information concerning a specific product could be attained within minutes.

Confidential, Baltimore, MD

Responsibilities:

• Used OS/390 Intrinsic functions along with ‘Windowing’ in place of file changes.
• I was responsible for all Confidential systems along with all COBOL programs and Confidential screens.
• All systems involved were successfully tested and implemented three months ahead of schedule.

Confidential, Annapolis, MD

Responsibilities:

• Worked with one other individual on the legacy batch and all Confidential on-line COBOL programs.
• Developed Batch and Confidential subprogram to be used by each module needing a century.
• This guaranteed every century produced used the same logic.
• Changes were completed and documented four months ahead of schedule.

Confidential, Montgomery, AL 1

Responsibilities:

• Worked with nine other programmers for year 2000 compliance for all of Confidential ’s state agencies.
• Conducted interviews at each state agency to inquire about any/all information regarding programs being run, along with files shared between agencies.
• Responsible for learning and running Computer Associate’s year 2000 tools ‘ Confidential 2000’ and ‘ Confidential 2000’ for identification of Librarian source programs, job streams and procedures which needed remediation.
• Responsible for obtaining copies of all code needing modification after the above-mentioned tools identified a year 2000 change was needed.
• Programs involved were COBOL.

Confidential, Chevy Chase, MD

Consultant

Responsibilities:

• Replaced associates moved from Confidential to PC based PEOPLESOFT while change was occurring.
• Responsible for implementation and maintenance of all COBOL programs involved with ‘DISC IRS’ system.
• Converted all reports stored on Confidential to BUNDL storage.

Confidential, Washington, DC

Consultant

Responsibilities:

• Moved all systems from VM to Confidential .
• Responsible for testing all applications on Confidential platform, after move and verifying all outputs.
• Established FOCUS database, to track all activities involved along with time spent so that all budgeted hours were correctly used.

Confidential, Chevy Chase, MD

Senior Programmer Analyst

Responsibilities:

• Responsible for all enhancements and trouble-shooting of Confidential system.
• Converted all COBOL programs to COBOL II.
• Assisted with implementation of Chevy Chases’ Confidential terminals into Safeway stores.