SUMMARY

• More than 12 years of proven IT work experience with Analysis, Development, Testing and supporting skills in IBM Mainframe. The entire professional career is being made out of continuous achievements. Experience in the Mainframe skills is being built up during my entire professional tenure.
• Great exposure to Development and Production Support project involving Mainframe technology.
• Excellent analytical and hands - on skill in COBOL, JCL, DB2, IMS, VSAM, REXX, CICS.
• Good understanding of IBM printing utilities like AFP, XEROX.
• Capable of automating manual activities using REXX and IBM Utilities.
• Extensive knowledge on IBM tools like File-Aid, Sentry, Changeman, Endeavor, Xpeditor, and Intertest.
• Good exposure to scheduling tools like CA7, ESP, CA-DE
• Exposure to Informatica is an added advantage.
• As a technical lead, capable of handling team of 10-15 people and perform activities like status reporting, project estimation and resource planning.
• Good understanding of SDLC, both agile and waterfall.
• Shows excellent Verbal and Client communication skills.
• Extensive experience in Banking & Finance and Retail domain.

TECHNICAL SKILLS

Languages: COBOL, JCL, VSAM, CICS, INFORMATICA

IBM Tools/Utilities: REXX, FILE-AID, CHANGEMAN, IDCAMS, DFSORT, ENDEAVOR, XPEDITOR, INTERTEST, AFP, XEROX, SPUFI, INFOMAN, CLEAR CASE, SENTRY.

Database: DB2, IMS

Platforms: IBM Mainframe Z/OS, Windows

Scheduler: CA7, ESP, CA-DE, UC4

Ticketing Tools: Service Now, SMART

Domains: Banking & Financial, Retail

PROFESSIONAL EXPERIENCE

Confidential

Senior Mainframe Developer

Responsibilities:

• Provide level-3 support for Merchandising/Sales-Audit/Logistics Batch application which involves mainframe jobs and informatica workflows.
• Monitor and resolve any critical mainframe job failures.
• Analyze and identify permanent fix for repeated mainframe job failures.
• Acknowledge and resolve tickets raised by business team in respective application.
• Create adhoc JCL/Cobol program to provide temporary solution for any production issue.
• Sales/Return data are processed and stored in DB2 database. Based on business needs, provide the data from DB2 by running select/join queries in SPUFI.
• For SAKS, TLTS is a CICS front end real time trickling system which pulls data from Stores Controllers to Mainframe for daily Sales/Return processing. Sometimes due to controller issue, data may not be pulled which may cause financial loss to the company. To avoid this, created a job using COBOL/JCL/VSAM which runs every hour to make sure data is trickling and sent out alert in case any of the stores are not trickling for the past hour.
• Pricing data for Lord&Taylor flows from PCW system (Oracle) to Mainframe via Tandem. Mainframe pushes these pricing data to the store controllers. There is an existing issue in Tandem which stops regional pricing flow to Mainframe. To fix this, created a job using COBOL/JCL/VSAM/UNIX which will query the oracle database and pull the regional pricing directly to the mainframe file.
• Request will be placed by the business to update vendor information in merchandising mainframe file on a weekly basis. Using JCL/Unix script, this has been automated. Business will place the file in a common Unix server path. Unix job will pull this file and place it in mainframe. A weekly job has been scheduled in mainframe which will read this file and update the required merchandising file.
• Daily Settlement file for SAKS banner goes to Bank from Mainframe via UC4 scheduler. UC4 job is scheduled to run every day after midnight 12:00 AM to pick up the settlement file. In case Mainframe settlement file delayed, UC4 job was picking previous day file and sending it to the Bank for settlement. To avoid this issue, UC4 job was scheduled to run based on trigger file from Mainframe. Added a step in settlement JCL which will create a trigger file at the end of the job. UC4 will delete the trigger file once the settlement file is sent to the Bank.
• Fashion application is a Lord and Taylor system where in each Item will be categorized into a Style number. During Reclass activity, when an Item moves from one Dept/class to another one, corresponding Style number in Fashion should get moved accordingly. There is a known issue in which specific styles are not moving after reclass. In order to fix this, created a tool (JCL/COBOL) which will identify those styles and correct them in Fashion.
• Identified and applied permanent fixes for the mainframe jobs that were failing with Data Exception (S0C7).
• Made schedule changes to the jobs those where running into DB2 deadlock with another jobs. Schedule changes are applied to ESP where the jobs are scheduled to run.

Confidential

Senior Mainframe Developer

Responsibilities:

• Involved in analyzing existing COBOL DB2 programs in merchandising applications to handle new DC type.
• Created High-level and Low-level design document which outlines the changes needed for merchandising application to handle UDC.
• Involved in the modification of impacted COBOL DB2 programs with required UDC handling code changes.
• Involved in Unit testing and prepared Unit test cases for UDC changes.
• Deployed the UDC changes in QA and Production. For Deployment, tools like Endeavor were used.
• RAMP report to support UDC implementation. RAMP report is used to pull inventory details after UDC was implemented. Created necessary JCL and Queries to pull inventory details from DB2 tables.
• Introduced REXX tools to automate manual activities like mainframe file creation, GDG creation, Test Job creation during UDC testing.
• As a Technical lead, managed more than 10 people by planning and assigning work to the team members.
• Coordinating with onshore during testing and implementation of UDC changes.

Confidential

Mainframe Tech Lead

Responsibilities:

• Involved in creating Technical Design document creation in order to identify the changes needed for this conversion.
• Created new AFP Tags for statements in CICS screen, new AFP control cards and new template COBOL program.
• Created Unit test cases for the changes that were done.
• Created Changeman/Infoman packages to install the changes in UAT/Production.
• Analyzed and identified the COBOL programs/JCL that were impacted due to this.
• Created technical design document to outline the changes required for rebranding.
• Made COBOL/JCL changes that were needed to handle new Brand indicator.
• Involved in Unit testing and created necessary Unit Test Cases document.
• Conducted code and unit testing walk thru before implementation.
• Created Changeman/Infoman packages to install the changes in UAT/Production.