1. AS/400 Migration Wei Lan wlan@microsoft.comConsultant Microsoft Technology Center

2. Issues with the AS/400 or AS/400 applications, that are common to a lot of AS/400 customers 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

3. Migration.. But How?

4. Migration Strategies

5. Redesign – New Functionality Migration Strategies Re-platform Applications Wrap or Front-end Applications Benefits 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 Move applications from mainframe environment to Windows environment without change Examples Recompile source, use CICS emulator ISV app migration Redesign application for Windows platform Examples Rewrite CICS application in.NET Convert DB2 app to SQL Server Faster Risks

6. Replace mainframe application with a new native.NET application. Either individual applications or whole environment. Advantages:Caveats: 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. New Design, New Application Big Bet, Big Bang !! Risks inherent in any large scale new software development project. Strategy Definition

7. Case Study - Countrywide Financial Corporation

8. Background Countrywide Financial: leading provider of consumer and business financial services in U.S.

9. 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…

10. 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

11. 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

12. 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.

13. Case Study - Presidential Life Insurance

14. 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.

15. 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.

16. Solution Migrate to Fujitsu NetKicksNetCOBOLfor.NET on Windows Server 2003. 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

17. Transaction Manager: CICS Programming Language: COBOL Screens: BMS Programming Language: NetCOBOL for.NET Screens: ASP.NET Transaction Manager: NetKicks (“Executive” Runtime) Fujitsu CICS & COBOL Tools NetKicks 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 NetCOBOLfor.NET NetCOBOL ® for.NET Fully integrated with Visual Studio.NET Access to the.NET Framework Verifiable COBOL Interoperability with other.NET Languages

18. Benefits Data acquisition from source systems and integration Data acquisition from source systems and integration Data transformation and synthesis Data transformation and synthesis Data enrichment, with business logic, hierarchical views Data enrichment, with business logic, hierarchical views Data discovery via data mining Data discovery via data mining Data presentation and distribution Data presentation and distribution Data access for the masses Data access for the masses Integrate Analyze Report Less Migration Time Faster Building New Applications with Visual Studio.NET SQL Server Reporting Service with Embedded in Business Intelligence functions.

19. and enhance with GUI controls BMS Converted to Web Forms

20. What We Can Help

21. Enterprise Migration View MS&PARTNERS Evaluate Plan Build Deploy Operate Preliminary Assessment Migration Workshop Application Proof of Concept Port Application & Infrastructure Issues Analysis Preliminary Migration Plan Impact Reviews Final Migration Plan Code Migration Port Testing Benchmarks Infrastructure Proof of Concept Field Test Deployment & Support Plan Infrastructure & Support In Place Full Application Roll Out User & Admin Training Deployment & Project Review Evolution Plan MICROSOFT PRODUCT GROUPS FeedbackFeedbackFeedback

22. Migration Team Customer Executive Committee QualityAssurance Architecture OversightArchitecture Oversight Infrastructure OversightInfrastructure Oversight Proof-Of-Concept LabProof-Of-Concept Lab IT Department Migration Project Office In-houseStaffSpecialtyVendors

23. © 2005 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.