IBM Mainframe Migration to Windows

Download Report

Transcript IBM Mainframe Migration to Windows

AS/400 Migration
Wei Lan
[email protected]
Consultant
Microsoft Technology Center
Migration Drivers
High cost of operations, upgrades
High price-performance of AS/400 ecosystem
Lack of flexibility to meet business needs
Long time-to-market for new products – slow to change
Poor Supportability
Issues with the AS/400 or AS/400 applications, that are
common to a lot of AS/400 customers
Migration.. But How?
Migration Strategies
Migration Strategies
Redesign – New Functionality
Redesign application for
Windows platform
Examples
Rewrite CICS application in .NET
Convert DB2 app to SQL Server
Re-platform Applications
Move applications from mainframe
environment to Windows environment
without change
Examples
Recompile source,
use CICS emulator
ISV app migration
Wrap or Front-end Applications
Leave application on mainframe, add
front-end on mainframe or Windows to
provide additional functionality or UI
Examples
IIS talking to DB2 on mainframe
Three tier architecture
New Design, New Application
Big Bet, Big Bang !!
Strategy Definition
Replace mainframe application with a new native .NET application.
Either individual applications or whole environment.
Advantages:
Design for improvement in performance.
Takes advantage of .NET functionality.
Clean-room advantages – all code can be fully documented,
latest devices can be supported, etc.
Modern current design versus layers of modifications
over many years of evolution.
Caveats:
Risks inherent in any large scale new software
development project.
Case Study Countrywide Financial
Corporation
Background
Countrywide
Financial:
leading
provider of
consumer and
business
financial
services in U.S.
Background
Company Profile: A leading provider of consumer
and business financial services in U.S.
Its AS/400 Tax Service System tracking
Countrywide’s six million mortgage loans – a
portfolio that’s growing by 100,000 loans every
month.
Countrywide was close to using all available
resources on the AS/400.
The ONLY choice was to purchase another AS/400
solution for another US$ 2.3 million. But…
Challenge
Could not know whether it would be buying
enough power/resources for the next few years.
Company may quickly outgrow the additional
system.
Old problems with AS/400 still exist:
8 hour nightly window for batch jobs
Still “Green screen” ?
“We want a solution that could scale
with the increase in Coutrywide’s
portfolio growth and also maximize
the ROI on our investment .”
- Paramjit Chumber, Senior V.P. and CIO, Countrywide Financial
Solution
Work with Microsoft Consulting Service (MCS) to
redesign the whole system to distributed Windows
platform with .NET Framework
Migrate and create 15 new Tax service applications
within 20 months
Web Farm
ASP.NET
App Farm
Enterprise Service
Data Sources
SQL Server 64bit
Benefits
Save US$ 1.7 million over the cost of expanded
AS/400 solution:
US$1.2million (savings in hardware and software)
+
US$500,000 (annual savings of maintenance fees)
Productivity increases 43% measured by the number
of loans it process -> $2.5 million increased revenues
Plan its infrastructure investments more effectively,
buying only as much as need now, and scaling out
with additional servers only as needs require.
Case Study Presidential Life Insurance
Background
Company Profile: Founded in 1965 and located in
New York, Presidential Life Insurance is a leading
provider of annuities and life insurance products to
financial service professionals in U.S.
The legacy AS/400 system that supports the life
insurance operations comprises over 160 screens
and over 650 COBOL programs.
Challenge
AS/400 are expensive machines to purchase and
maintain – often an order of magnitude more than
similarly powered PC configurations.
Independent Software Vendors (ISVs) are no longer
developing add-on tools for the platform.
The software on the AS/400 was perceived to be
falling behind that available on other platforms in
terms of usability and flexibility of data reporting.
Solution
Migrate to Fujitsu NetKicks, NetCOBOL® for .NET
on Windows Server 2003.
Started the implementation of their migration plan
for all systems in the summer, 2004 and complete
at March, 2005
Fujitsu CICS & COBOL Tools
Transaction Manager:
CICS
Programming Language:
COBOL
Screens:
BMS
NetKicks




TM
A BMS map to ASP.NET wizard
An “EXEC CICS” program translator wizard
A NetKicks “Executive” runtime
A Property Manager for PCT, MCT and FCT
Transaction Manager:
NetKicks
(“Executive” Runtime)
®
NetCOBOL for .NET




Fully integrated with Visual Studio .NET
Access to the .NET Framework
Verifiable COBOL
Interoperability with other .NET Languages
Programming Language:
NetCOBOL for .NET
Screens:
ASP.NET
Benefits
Less Migration Time
Faster Building New Applications with Visual
Studio.NET
SQL Server Reporting Service with Embedded in
Business Intelligence functions.
Analyze
Integrate


Data acquisition from
source systems and
integration
Data transformation
and synthesis


Data enrichment, with
business logic,
hierarchical views
Data discovery via data
mining
Report


Data presentation and
distribution
Data access for
the masses
BMS Converted
to Web Forms
and enhance with
GUI controls
What We Can Help
Enterprise Migration View
M
S
&
P
A
R
T
N
E
R
S
Plan
Evaluate
Preliminary
Assessment
Build
Application &
Infrastructure Code Migration
Issues Analysis
Deploy
Operate
Field
Test
Full Application
Roll Out
Migration
Workshop
Preliminary
Migration Plan
Impact Reviews
Port Testing
Benchmarks
Deployment
& Support Plan
User & Admin
Training
Application
Proof of
Concept Port
Final
Migration Plan
Infrastructure
Proof of
Concept
Infrastructure
& Support
In Place
Deployment &
Project Review
Evolution Plan
Feedback
Feedback
Feedback
MICROSOFT PRODUCT GROUPS
Migration Team
Customer Executive Committee
IT Department
Migration Project
Office
In-house
Staff
Quality
Assurance
•Architecture Oversight
•Infrastructure Oversight
Specialty
•Proof-Of-Concept Lab
Vendors
© 2005 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.