Kather Ali Jamal Mohamed

Mobile: +1-201-***-****

E-mail: ac0jme@r.postjobfree.com

Career Objective

To work in a challenging environment that provides opportunity to learn key technologies, be an effective team player in supporting, managing projects and to be an asset for the organization by delivering to the best of my capabilities.

Experience Summary

Have more than 7.5 Years of experience in IBM mainframe.

Have demonstrated experience and knowledge in COBOL, JCL, VSAM, DB2, CICS and IMS DB.

Developed some important automation tools such as ‘Impact Analyzer’, ‘Database Management Tool’, ‘Program Analyzer’ and ‘Mainframe Elevation Tool’ using REXX routine.

Involved in Analysis, Design, Development, Testing, Implementation and Team Coordination.

Handled many projects with defect free releases.

Identified many areas of improvement, good practices and standards to be followed in projects.

Worked on various projects for the international clients such as Walmart, EmblemHealth, AVON and Sentry Insurance.

Demonstrated ability to work as a very good team leader and team player.

Strong analytical and problem solving capabilities with Good communication. Educational Qualifications

Title of the Degree with Branch College/University Year of Passing M.E. in Communication Systems Kumaraguru College of Technology, Coimbatore.

2008.

Technical Skills

Hardware / Platforms

Z/OS

Technology Mainframe

Programming

Languages

COBOL, JCL, REXX

Databases DB2, VSAM, IMS-DB, INFORMIX

Transaction Server CICS

Tools ISPF/PDF, Change-man, File-Aid, File-Manager, XPEDITER, CA7 Utilities QMF, SPUFI and IBM Utilities

Certifications

External Certification – AICPCU – INS 21 (Property and Liability Insurance) Cognizant Certified Professional in COBOL and JCL

Brainbench Certification – DB2 Programming

Brainbench Certification – VSAM

Relevant Project Experience

Organization: Cognizant Technology Solutions

Project #1

Title EDPS RENOVATION PROJECTS

Client EmblemHealth

Operating System Z/OS

Technologies COBOL, JCL, VSAM, CICS, File-Aid, CA7 Team Size 4

Role Onsite Team Lead

Period July 2016 – Till date

Project Objective

As part of transition from Risk Adjustment Process System (RAPS) to Encounter Data Processing System

(EDPS), the vendors will be submitting the claims/encounters to CMS in 837P (Professional claims) or 837I (Institutional claims) format.

To process the new claims/encounters in the original claims 837 file (837P/837I format) for the vendor CCS (Complex Care Solutions). To process the claims/encounters in the new linked and unlinked chart review files (837P/837I format) for the vendors Inovalon EPass (Electronic Patient Assessment Solution Suite), DDDS (Date Driven Delivery Systems) and CCS. Project Description

EmblemHealth (EH) will receive three separate GDG files (in 837P/837I format) from CCS (Complex Care Solutions) via MFT (Managed File Transfer) process. One is the original claims 837 file (vendor- type code 0309), other one is the linked chart review file (vendor-type code 0314) and another one is the unlinked chart review file (vendor-type code 0322). The linked chart review files have the claim numbers, which are present in the EH system. The unlinked chart review files do not have the claim numbers present in the EH system. The requirement is to create a new job for processing the new claims/encounters with max of 12 diagnosis codes present in original claims 837 file. The remaining diagnosis codes for the same claim number would be processed through chart review files. Two new jobs would be created for processing the linked and unlinked chart review files separately. The jobs will validate the input data and create the EDI837 file, which will be sent to CMS (Centers for Medicare

& Medicaid Services) via NDM (Network Data Mover) process. The CMS will adjudicate the claims/encounters submitted and send the 999, 277 and MAO (Medicare Advantage Organization) responses (approved/rejected) back to EH. EH will process the response files (GDG files) to identify the number of approved/rejected claims and the error messages for the rejected claims. EH will also send back the responses to the CCS vendor via FTP process. EmblemHealth (EH) will receive two separate GDG files (in 837P/837I format) from Inovalon EPass

(Electronic Patient Assessment Solution Suite), one with linked chart reviews (vendor-type code 0914) and the other with unlinked chart reviews (vendor-type code 0922) via MFT process. Similarly, EH will receive two separate GDG files (in 837P/837I format) from DDDS (Date Driven Delivery Systems), one with linked chart reviews (vendor-type code 0513) and the other with unlinked chart reviews (vendor- type code 0521) via MFT process. The requirement is to create four new jobs for processing the linked and unlinked chart review files. The jobs will validate the input data and create the EDI837 file, which will be sent to CMS via NDM (Network Data Mover) process. The CMS will adjudicate the claims/encounters submitted and send the 999, 277 and MAO responses (approved/rejected) back to EH. EH will process the response files (GDG files) to identify the number of approved/rejected claims and the error messages for the rejected claims. EH will also send back the responses to the Inovalon/DDDS vendor via FTP process.

As part of development, new jobs are created for chart review processing and original claims 837 file processing, and the impacted programs/procs which are common for all vendors are modified to accept the new vendors/types. As per the requirement, new trigger jobs are also created to trigger an original claims processing jobs and the chart review processing jobs, only when the input GDG files are received from vendors.

Role and Responsibilities

Involved in coordinating and guiding the mainframe team in all the phases.

Involved in gathering the requirements, identifying the impacted mainframe components, analyzing the impact of the change with the existing structure and then implementing the same on the system.

Involved in Construction, Coding, Unit testing and Integration Testing.

Involved in multiple design/development module calls, which requires a proper understanding of the business.

Involved in preparing the customized and special project reports to meet customer demands.

Involved in reviewing the code for compliance of standards and ensuring proper testing of the code before deployment.

Involved in preparing and reviewing the Impact Analysis Documents, Design Documents, Test scripts and Implementation documents.

Involved in analyzing the quality process and innovating new methods to improve the process.

Involved in analyzing real time environmental and data issues in production.

Participated in daily status calls, weekly and biweekly meetings.

Shared the knowledge with team members in an effective way. Project #2

Title HOSRVH04 INFORMIX DATABASE MIGRATION

Client Walmart

Operating System Z/OS

Technologies COBOL, JCL, INFORMIX, DB2, IMS-DB, VSAM, CICS, File-Aid, CA7 Team Size 6

Role Team Lead

Period Aug 2015 – May 2016

Project Objective

To migrate the Informix databases of the Unix server hosrvh04 to some other database such as DB2 or Cassandra, and also to migrate the Unix server to Linux server. Project Description

There are totally 59 Informix databases in the Unix server hosrvh04. This project is to migrate all the 59 Informix databases to some other database such as DB2 or Cassandra, and also to migrate the Unix server to Linux server. As part of Mainframe Impact analysis, the impacted mainframe components have been identified by searching the server name hosrvh04, its alias name hosrvn01, and all the 59 databases in all the mainframe libraries, and also by doing Source Scan (scanning tool present in Walmart environment) for each database name or hosrvh04/hosrvn01. The Informix database is accessed by mainframe only with the topend name, which is used for connecting the Unix server. So, the impacted mainframe components have also been identified by searching all the topend names shared by Unix team, as part of Mainframe topend analysis. There are some CA7 jobs which trigger the Unix scripts, which in turn access the Informix database. These CA7 jobs and the parms present in the jobs (which contain the server name and directory path with script) are identified as part of Mainframe impact analysis.

As part of Design phase, the alternative database for the existing Informix database has been identified and finalized with the help of SME. There are number of tables present in each Informix database. In some cases, all the tables present in an Informix database have been migrated to only one database such as Cassandra database. In some other cases, some of the tables of an Informix database have been migrated to DB2, and other tables of the same database have been migrated to Cassandra or Teradata. As part of solution approach, in some cases, the alternative solution is to directly access the alternate database such as DB2 or Teradata or Cassandra. In some other cases, the alternative solution is to invoke Web service call from mainframe to access the database. The Web service call can be invoked from CICS program to access the database or it can be invoked from Java Application which in turn will call CICS program to access the database. There are some FTP steps present in mainframe jobs which are used to transfer the files from mainframe to Unix or from Unix to Mainframe. As the Unix server is migrated to Linux server, the FTP step has been changed to SFTP (Secure FTP) as suggested. There are some inactive mainframe jobs, inactive includes, inactive parms, and inactive programs captured as part of Impact analysis. There are few report creating jobs for which the reports are not active. The above said inactive components have been identified for decommission as part of design phase. As part of remediation phase, each impacted component has been developed (modified or newly developed), tested (Unit testing, Integration testing within mainframe, and System Integration testing across platform) and implemented in production. There are some new programs created for handling the alternative approach such as Web service call or accessing Cassandra/DB2 database through new program instead of accessing Informix database through existing parm. The CA7 jobs which trigger the Unix scripts which in turn access the Informix database, are remediated for changing the server name

(Unix to Linux server) and the directory path name for the impacted scripts. As part of decommission phase, the inactive mainframe jobs, inactive includes, inactive parms, inactive programs and report creating jobs for which the reports are not active have been decommissioned. Role and Responsibilities

Involved in coordinating and guiding the mainframe team in all the phases.

Involved in gathering the requirements, identifying the impacted mainframe components, analyzing the impact of the change with the existing structure and then implementing the same on the system.

Involved in Construction, Coding, Unit testing and Integration Testing.

Involved in multiple design/development module calls, which requires a proper understanding of the business.

Involved in preparing the customized and special project reports to meet customer demands.

Involved in reviewing the code for compliance of standards and ensuring proper testing of the code before deployment.

Involved in preparing and reviewing the Impact Analysis Documents, Design Documents, Test scripts and Implementation documents.

Involved in analyzing the quality process and innovating new methods to improve the process.

Involved in analyzing real time environmental and data issues in production.

Participated in daily status calls, weekly and biweekly meetings.

Shared the knowledge with team members in an effective way. Project #3

Title STORE NUMBER EXPANSION

Client Walmart

Operating System Z/OS

Technologies COBOL, JCL, VSAM, DB2, IMS-DB, REXX, CICS, File-Aid, CA7 Team Size 9

Role Team Lead

Period July 2014 – July 2015

Project Objective

To enhance the functionalities of the mainframe system to increase the length of Store Number from 4 digits to 5 digits.

Project Description

Walmart expands its stores all over the world. Currently the store number fields occupy only up to 9999 stores. This project is to change the store number field in order to occupy a minimum of 32,767 stores. So, the existing store number field with the picture clause S9(4) COMP will not be changed, as it occupies 32,767 stores. The store number field with S9(4) COMP-3 will be replaced by S9(5) COMP-3, as both of them will occupy 3 bytes. The store number field with 9(4) or X(4) will be changed to 9(9) COMP in some cases, where it is feasible. In some other cases, the fillers in the file layout will be used to expand the store number field from 9(4) or X(4) to 9(5) or X(5). There are some other cases with different picture clauses, which will be handled properly such that it will not impact any component. In order to implement this project, all the impacted files, databases, copybooks, programs, procedures, includes and JCLs have been identified by analyzing the components. As there are so many components ranging more than thousand components, the implementation will be done phase by phase. The required changes in the components will be developed and tested phase by phase. The wrapper steps are inserted at the output of the implemented jobs in order to convert the store number field from new 5-digit format to old 4-digit format, so that the implemented jobs will not impact other jobs which will be implemented at the next phases. The wrapper steps are also inserted at the input of the implemented jobs in order to convert the store number field from old 4-digit format to new 5-digit format, so that the implemented jobs will not be impacted by other jobs which will be implemented at the next phases. Once all the components are implemented at the final phase, then the wrapper steps will be removed from all the components. Role and Responsibilities

Involved in gathering the requirements, analyzing the impact of the change with the existing structure and then implementing the same on the system.

Involved in Construction, Coding, Unit testing and Integration Testing.

Involved in multiple design/development module calls, which requires a proper understanding of the business.

Involved in preparing the customized and special project reports to meet customer demands.

Involved in reviewing the code for compliance of standards and ensuring proper testing of the code before deployment.

Involved in preparing and reviewing the Impact Analysis Documents, Design Documents, Test scripts and Implementation documents.

Involved in analyzing the quality process and innovating new methods to improve the process.

Involved in analyzing real time environmental and data issues in production, and coordinating with the team.

Participated in daily status calls, weekly and biweekly meetings.

Shared the knowledge with team members in an effective way. Project #4

Title BILLING INVOICE DATA SYSTEMS (BIDS)

Client Avon Products Inc.

Operating System Z/OS

Technologies COBOL, JCL, VSAM, DB2, IMS-DB, CICS, REXX, Change-man, File-Manager Team Size 5

Role Team Member

Period Oct 2012 – June 2014

Project Objective

To enhance the functionalities of the mainframe system (BIDS) such as to increase the length of Finished Stock Code and to provide the permanent solutions to the existing production incidents. Project Description

Avon Products Inc., Brazil has the project for providing support and maintenance of most heterogeneous collection of application modules such as BIDS, SIR, Commissioning, etc. The most complex and critical application is BIDS (Billing Invoice Data Systems), a Billing system which handles all billing related tasks and generates & prints the invoices. It’s also responsible for payments to Avon by Representatives. The BIDS application is completely developed on Mainframe using COBOL, JCL, DB2, IMS-DB, VSAM and CICS.

There are some huge enhancement projects such as to increase the length of Finished Stock Code in all the systems and programs. In order to implement this project, all the impacted files, tables, programs, procedures and JCLs have been identified by analysis. The Innovation tools such as ‘Impact Analyzer’,

‘Database Management Tool’ and ‘Program Analyzer’ developed by the Associate, have been very useful to identify the impacted components. Then the required changes in all the impacted components have been implemented and tested.

As the BIDS application is very critical for the business of AVON, it should be supported and maintained properly. And it is very important to provide the permanent solutions to the existing production incidents. In order to achieve it, the reported issue has been analyzed thoroughly to identify the root cause, and then the permanent solution has been implemented and tested. Role and Responsibilities

Involved in Requirement Analysis, Impact Analysis and Root Cause Analysis.

Involved in Construction, Coding, Unit testing and Integration Testing.

Involved in preparing and reviewing the Impact Analysis Documents, Design Documents, Root Cause Analysis Documents, Test scripts and Implementation documents.

Involved in reviewing the code changes done by team members and make sure that the codes are optimized and all requirements are implemented.

Involved in estimation of the projects.

Involved in fixing the production incidents.

Involved in developing the automation tools for the regular and repetitive process.

Participated in weekly and biweekly meetings.

Shared the knowledge with team members in an effective way. Project #5

Title RATE REVISION & ENHANCEMENT PROJECTS

Client Sentry Insurance, USA

Operating System Z/OS

Technologies COBOL, JCL, VSAM, DB2, REXX, File-Aid, XPEDITER, Easytrieve Team Size 5

Role Team Member

Period Nov 2010 – Sep 2012

Project Objective

To develop and enhance the functionalities related to online-screen navigations, batch processing, documerge forms and EDW.

Project Description

Sentry NSA is having two applications - AutoLink and Mainframe. AutoLink is a web based application used to create New Business Application for Non-Standard P & C Automobile Insurance Policies. This application interacts with various components like JBilling Component (for applying fees on the premiums for the pay options based on the product and insured information provided), and JRater

(rating the premiums for the products and pay options). AutoLink is supported by Mainframe system that houses the policy information, forms and business rules tables. All transactions including new business, endorsement and renewal are done in mainframe via CICS screen. Major processes including Billing are handled in mainframe environment.

Some of the modules were development modules to introduce some functionality such as introducing a new company, new product and new policy type. Some of the modules were enhancement modules to enhance some functionality such as changing the insurance score vendor, allowing the particular credit/discount, changing the order of display in the forms, passing some important data to EDW and so on.

Role and Responsibilities

Involved in Requirement Analysis, Impact Analysis and Root Cause Analysis.

Involved in Construction, Coding, Unit testing, Integration Testing and Regression Testing.

Involved in preparing and reviewing the Impact Analysis Documents, Design Documents, Root Cause Analysis Documents, Test scripts, Elevation documents, Conditional forms and Implementation documents.

Involved in reviewing the code changes done by team members and make sure that the codes are optimized and all requirements are implemented.

Involved in estimation of the projects.

Involved in fixing the production incidents and existing production incidents.

Involved in developing the automation tools for the regular and repetitive process.

Participated in daily status calls, weekly and biweekly meetings.

Given KT to the new team member in an effective way. Project #6

Title MAINFRAME ELEVATION TOOL

Client Sentry Insurance, USA

Operating System Z/OS

Technologies REXX, JCL

Team Size 2

Role Team Member

Period Aug 2010 – Oct 2010

Project Objective

To automate the mainframe elevation process for elevating the program changes from one region to another region.

Project Description

In order to reduce the elevation time and to increase the productivity, a mainframe elevation tool was developed to automate the elevation process for elevating the program changes from one region to another region. Most of the modules were developed using Rexx (panels and macros) language. The project changes done with the project-Id will be retrofitted into the program properly, which was the most complex module of this tool. The status bar was also used to show the current status of the elevation process during the execution of the elevation tool. This tool was one of the major innovation tool developed from sentry account.

Role and Responsibilities

Involved in Requirement Analysis and Impact Analysis.

Involved in Construction and Coding (involves designing a lot of modules, sequence flow, status flow, and integration of different modules).

Involved in Unit testing and Integration Testing.

Involved in preparing the Design Documents, Test scripts and Elevation documents.

Involved in preparing the KT document for this automation tool, and showing the demo to onsite and offshore teams.

Shared the knowledge with team members in an effective way. Project #7

Title VSAM TO DB2 MIGRATION

Client Sentry Insurance, USA

Operating System Z/OS

Technologies COBOL, JCL, VSAM, DB2, File-Aid

Team Size 4

Role Team Member

Period Feb 2010 – Jul 2010

Project Objective

To migrate from VSAM files to DB2 tables.

Project Description

All the master and history policy data were moved from VSAM files to DB2 tables in order to improve the security and to increase the concurrency and integrity. The format of VSAM file variables is different from the format of DB2 table variables. In order to migrate from VSAM to DB2, the existing programs were modified in such a way that the policy data would be processed from DB2 tables instead of VSAM files.

Role and Responsibilities

Involved in Requirement Analysis and Impact Analysis.

Involved in Construction, Coding, Unit testing and Integration Testing.

Involved in preparing the Impact Analysis Documents, Design Documents and Test scripts.

Involved in preparing the KT document.

Innovation Tools Developed

Organization: Cognizant Technology Solutions

Tool#1

Title IMPACT ANALYZER

Client AVON, Brazil

Operating System Z/OS

Technologies REXX

Tool Description

The changes in a program might need corresponding changes in the impacted Procs and JCLs. Similarly, the changes in a Proc and/or JCL might need corresponding changes in other impacted components. For this, we need to find the interconnectivity between Programs, Procs and JCLs. The program can be Cobol program or Cobol-DB2 program or Cobol-IMS-DB program or Assembler program or Eztrieve program. In most of the cases, the Cobol-DB2 program is called by DB2-library member or CTL-library member, which is invoked by Proc, which is again invoked by JCL. In some of the cases, the Cobol-DB2 program is directly called by JCL. The other programs such as Cobol-IMS-DB program, Assembler program, Eztrieve program are invoked by Proc or JCL directly. Generally, a program can be called by multiple Procs and/or JCLs. A Proc can be called by multiple JCLs. This existing hierarchy of interconnectivity between Programs, Procs and JCLs will complicate the process to find their interconnectivity. Moreover, the symbolic parameters are also used to mention the DB2LIB or CTLLIB member names, which will also complicate the search process. In order to find the interconnectivity between Programs, Procs and JCLs, a tool named “Impact Analyzer” is developed using REXX routine such that any user can use this tool easily. For any given Program, the tool gives the impacted Procs and JCLs. For any given Proc, it gives the impacted JCLs and Programs. And for any given JCL, it gives the impacted Procs and Programs. By using this tool, the impacted components of a program/proc/Jcl will be found in few seconds. Tool#2

Title DATABASE MANAGEMENT TOOL

Client AVON, Brazil

Operating System Z/OS

Technologies REXX

Tool Description

The DB2 and IMS-DB are the most important databases used in Mainframe. All the programs are accessing the databases for inserting/updating/replacing/deleting/selecting the records needed. If the data in a database are corrupted by some program, it will also impact all other programs as well as other systems. In order to identify the issue causing programs and the impacted programs, it is needed to have a list of programs which are inserting/updating/replacing/deleting/selecting the particular database.

Manually finding the list of programs is the effort and time consuming process. Therefore, a tool named

"Database Management Tool" is developed using the REXX routine such that it will provide the list of programs which are inserting, updating, replacing, deleting and selecting the given database (DB2 or IMS-DB).

Tool#3

Title PROGRAM ANALYZER

Client AVON, Brazil

Operating System Z/OS

Technologies REXX

Tool Description

The changes in a Cobol program might impact the databases such as DB2 and IMS-DB accessed by the program. There might be changes required in the sub-programs as well. Before making any changes, it is important to understand the existing functionality of the program. A larger Cobol program would access multiple databases and also call multiple sub-programs. In order to understand the existing functionality of a larger program, it is better to identify the databases which are inserted, updated/replaced, deleted and selected by the program, and the sub-programs which are called by the program.

Manually finding them is the effort and time consuming process. Therefore, a tool named "Program Analyzer" is developed using the REXX routine such that it will provide the list of databases (DB2 and IMS-DB) which are inserted, updated/replaced, deleted and selected by the given program, and the list of sub-programs called by the given program, within in few seconds. Tool#4

Title MAINFRAME ELEVATION TOOL

Client Sentry Insurance, USA

Operating System Z/OS

Technologies REXX, JCL

Tool Description

In order to reduce the elevation time and to increase the productivity, a mainframe elevation tool was developed to automate the elevation process for elevating the program changes from one region to another region. Most of the modules were developed using Rexx (panels and macros) language. The project changes done with the project-Id will be retrofitted into the program properly, which was the most complex module of this tool. The status bar was also used to show the current status of the elevation process during the execution of the elevation tool. This tool was one of the major innovation tool developed from sentry account.

Personal Details

First Name : Kather Ali

Last name : Jamal Mohamed

Contact address : 2801 John F. Kennedy Blvd – Apt E22, Jersey City, NJ 07306 Contact number : +1-201-***-****

Mail Id : ac0jme@r.postjobfree.com

Thanks and Regards,

Kather Ali Jamal Mohamed

Contact this candidate