Category: Mainframe Projects

Project name: GCDM (Global Customer Data Management) Mainframe Project Abstract for Fresher’s
Software: IBM Mainframe in COBOL, JCL, CICS, IMS-DB, File-Aid

Description
This Project Comes Under Banking domain in software industry. It serves as a database of core Customers, Limits, Securities, Reference and Organizations, which can serve as a source of data to all the applications.
The primary function of CDU is to store customer data in a single regional repository and under a single profile, and to provide delivery and maintenance of that data via standard APIs. This provides the business with a common customer view, simplifies interfaces to warehouses, and protects applications from changes to the underlying database.

Developer Responsibilities:

1.  Formulation and estimation of maintenance and new functionality request.
2.  Construction of batch programs using COBOL, JCL
3.  Providing solutions to problems arising in the production.
4.  Preparation of Test case document
5.  Monitoring the status of the program till it runs on production successfully.

ENVIRONMENT: COBOL, JCL, IMSDB, CICS, FILE-AID.

Project Name : Annual Invoicing and Royalty on Mainframes

• Project Environment

1. Software:
2. Languages : SQL
3. Database : SQL Server 2005
4. Tools : Quality Center 9.0
5. O/s : Windows XP
6. Hardware: Pentium IV, 1GB RAM

Project Description:

The AIR (Annual Invoicing and Royalty) application is a reporting mechanism that creates annual invoices for new and renewal customers, change invoices (credit or amendment), and final invoices. It also produces financial reports such as revenues worksheet, income recognition and royalty reports, as well as other ad-hoc sales reports. AIR interfaces with various other Mainframe systems.
I individually worked on the entire module AIR Super-User Support Enhancements and few of the requirements for the module AIR Release 6.0

Contribution
• Preparing Test Design Specifications from Software Requirements Specifications.
• Preparing Test Scripts and uploading them into Test Plan present In Quality Center.
• Running triggers on each table identified for auditing and checking if the Audit Tables are reflected according to the operations performed.
• Running the weekly/Monthly job created in SQL.
• Sending the invoices to Oracle AR and verifying that the details are correctly reflected.
• Importing the CRM files and checking the validations thrown and the key fields returned.
• Running the Validation String corresponding to a particular validation failure message.
• Logging Defects into Quality Center

Mainframe Projects for final year Students & Freshers Environment

• Software:
• Languages : C# , SQL
• Databases : Microsoft Sql server 2005,
• Tools : Microsoft Visual Team Suit , Quality Center 9.0
• O/s: Windows 2003/XP/Vista
• Hardware: Pentium 1V, 512 MB RAM

Project Description:
A Mainframe system Technologies, plans, develops, implements, and maintains future-proof IT systems. This involves everything from software development and ERP systems through to application management and intelligent customer retention solutions.

Mainframe system is based on IBM mainframe technology. The product is rich in functionality for data enter scheduling operations, proven & robust through system’s own internal use of it. Different application areas are Master Data management, system master data, stream design management, runtime management, Reports.

Developer Contribution:
1 Analysis and Review of Business Requirements Specifications and Design Documents
2 Preparing Requirement Traceability Matrix from Business Requirements Specifications and Design Documents
3 Identifying Test Scenario’s, Written test cases and prepared bug reports for the various modules and Responsible for functional testing for Master Data, Stream design and Runtime modules
4 Identifying test input data by running sql queries in DB
5 Execution of Test Scripts
6 Create and maintain tests and test records.
7 Log defects, analyze defect data.
8 Deploying the Database, Application server, processing server and GUI at client environment
9 Executing User acceptance test scenarios for different modules like Master Data, Stream design, Runtime & Non Functional Requirements for system integration test on each new build or release
10 Performed Smoke Testing for the Application functionalities

1. Project Name :  Increment 1 Conversion Mainframe Project
2. Role              : Developer
3. Tools/Skills     : JCL, DB2, COBOL, IMS, CICS, VSAM, File Manager, Quality Center, Changeman, Intertest, Revolve, Mainframe Express 3.0 (Enterprise Edition)   And Micro Focus Net Express 5.0

• Identifying the impacted components (source code, JCL, Copybooks, Proc) as a part of the changes.
• Creation of new project on the Netexpress platform with all the impacted components and other dependencies (Files, copybooks etc) and then sharing with the team.
• Creation of Test plans.
• Unit testing of Batch and Online programs on both Mainframe (Base version having IMS calls) and NetExpress (Modified version having db2 calls) platforms.
• Dubbing of the code.
• Raising defects in Quality Center.
• Performing the Reviews of the test plans.

Project Scope:

         The project is a migration project for Migrating the current application from Mainframe to Micro Focus Enterprise Server. The Increment 1 Conversion involves the conversion of DB2 calls to SQl calls. The module s having the db2 calls were the base modules which reside on the mainframe system while the modules having the SQL calls were the modified modules which reside on the new platform. The final output of the converted modules should be exactly similar to the base modules.

1. Project Name : PSP-FM Card Processing System Mainframe Project
2. Role              : Tester
3. Tools/Skills     : JCL, DB2, COBOL, File Aid, spufi Quality Center, Expeditor.

Developer Responsibilities:

• Performing the Required Analysis based on business.
• Preparation of SIT / UAT Test Plans
• Conducting System Integration Testing.
• Preparation of Team’s Weekly/Monthly Status reports and Project Matrix. 

Project Scope: 

FM is the main posting and billing process for the U.S cardholder system. FM inputs, verifies, and applies all account activity (monetary and non-monetary) and posts the valid activity to the appropriate customer’s account. In addition, FM calculates interest charges, assesses fees, applies product charges and execute various other activates to supply billing information to the downstream applications for generating customer billing cycle statements. The File-Maintenance (FM) Application supports the account maintenance function of the Card Processing System. 

The PSP platform is built to execute core Fm through multiple events without interface with other applications, except Triad and Blaze. This allows for quicker turnaround of FM testing and more flexible run times