Modernizing Your IMS Environment Without an Application Rewrite Series Part 2: The IMS Application Stakeholders
0 likes227 views
This document discusses the modernization of IMS environments without rewriting applications, focusing on a migration strategy to DB2 using Syncsort's DL/2 tool. It highlights the challenges and risks of legacy IMS modernization, the benefits of transitioning to DB2, and the cost savings associated with reducing IMS support. The presentation also outlines a transparent migration process and provides insights into developing a business case for organizations considering this transition.
Modernizing Your IMS Environment Without an Application Rewrite Series Part 2: The IMS Application Stakeholders
- 1. Modernizing Your IMS Environment Without Rewriting Applications Part 2 of 3 Presenters Bill Bostridge and Mike Picou
- 2. Agenda • Notable 50th birthdays • Migrating to Db2 – If it was easy we would have done it years ago • Transparent Data Migration from IMS to Db2 • Application Developers and the Application stakeholders • Developing the Business Case • Q&A
- 4. • Founded in 1968 as Whitlow Computer Systems • Developed a new, faster Sort capability for the IBM mainframe • Was featured in a lead article in Computerworld in 1969 • “Syncing and sorting data” • The rest is history – Syncsort MFX is used by 84 of the top Fortune 100 company’s, with over 7,000 customers worldwide 1968 – Syncsort 4
- 5. Introducing Syncsort >7,000 customers 84 of the Fortune 100 Customers in >100 countries Headquarters: Pearl River, NY U . S . L O C AT I O N S • Burlington, MA; Irvine, CA; Oakbrook Terrace, IL; Rochester, MN G L O B A L P R E S E N C E • U.K., France, Germany, Netherlands, Israel, Hong Kong & Japan Big Iron to Big Data is a fast-growing market segment composed of solutions that optimize traditional data systems and deliver mission-critical data from these systems to next-generation analytic environments. 5 Global leader in Big Iron to Big Data
- 6. It distinguishes yesterday’s bellwethers from tomorrow’s disruptors Data is the bedrock on which businesses compete Data dictates the success or failure of companies based on how they own, access and analyze it to build new capabilities Data provides trusted insights that can produce better business results We believe that data makes the difference… 6
- 7. We use our experience so that you can quickly extract value from your critical data anytime, anywhere We organize data everywhere, to keep the world working Work more efficiently Grow faster Achieve more 7
- 8. • IMS has been a terrific workhorse for decades but the folks who wrote, maintain and support this platform are heading to retirement • Re-writing or re-platforming is a significant challenge • Many projects fail to complete or even get off the ground • IMS applications are often mission critical, so re-development is a daunting and highly risky undertaking • Decades of custom business logic is built into these applications – replicating this into new development is a huge task What are the challenges to legacy IMS modernization 8
- 9. • Bottom line, Status Quo is an easier ask, but at what risk to the organization? • How will your company replace IMS skills and application programming knowledge over the next few years? • Outsourcing support and application maintenance to 3rd parties? • The time to make a low risk move to DB2 is now!! Making a low risk move to Db2 9
- 10. • Transparent migration of the application data to Db2 with no change to application code • Eliminate on-going DBA and programming support for IMS DB • Consolidate DBA support to Db2 • Migrate IMS databases to Db2 at your own pace • Eliminate the high MLC costs of IMS DB and IMS support tools • No more IMS version upgrades as old versions go out of support by IBM • DL/2 fully supports IMS DB/DC and IMS CICS environments Syncsort DL/2 – a low risk migration strategy 10
- 11. • DL/2 is a combination of IMS to Db2 migration and mapping tools to migrate IMS segments to Db2 tables • DL/2 is also the replacement for the IMS Db stub program and acts as the interface between the IMS applications, which do not change and the migrated IMS data that is now residing in Db2 • DL/2 is a replacement for IMS DB and IMS support tools (IBM, BMC, Compuware etc) • DL/2 is not replicating data to Db2. DL/2 is replacing IMS DB so that all your production data is now residing in Db2 What is DL/2 11
- 12. DL/2: Transparent Migration Process Overview Before During After IMS NO DB2 YES DL2 Stub Application Program Static SQL Data in DB2? IMS Stub Application Program DL2 Stub Application Program IMS DB2 12
- 13. DL/2: Transparent Migration Process Overview Before During IMS NO DB2 YES DL2 Stub Application Program Static SQL Data in DB2? IMS Stub Application Program IMS 13
- 14. DL/2: Transparent Migration Process Overview Before During After IMS NO DB2 YES DL2 Stub Application Program Static SQL Data in DB2? IMS Stub Application Program DL2 Stub Application Program IMS DB2 14
- 15. What do we mean by Transparent Data Migration • No modifications, compiles or recompiles • Migrate at your own pace – one file at a time, multiple files • Environmental changes for batch JCL and CICS can be made non-disruptively in advance • Simple switch between IMS and Db2 for application testing • Fallback capability • Easiest and fastest route to Db2 and value delivery LOWEST RISK MIGRATION APPROACH – PROVEN TIME AND TIME AGAIN 15
- 16. • What are the benefits? • One less platform to maintain • Eliminate on-going DBA and programming support for IMS DB • Consolidation of application maintenance to Db2 /SQL skills, • Add new fields, new tables etc • Over time, rewrite components to native SQL – make an orderly move to modernize your applications • Eliminate replication – “one version of the truth” • Eliminate enforced IMS DB upgrades – V13, V 14 V15 and so on… • Eliminate software licensing costs for IMS DB and IMS tools • Reduce reliance on IMS as skills head to retirement Consolidation from IMS to Db2 with DL/2 16
- 17. Question? – Does you organization just want to remove IMS DB and the associated support overhead and on-going licensing costs? “We just want to get out of IMS” OR We would like to get our IMS data into a relational model in DB2 to further the life of the applications and support new business initiatives “We want to be in DB2” Benefit to IMS application user community 17
- 18. 18 Migration options Complexity/Time/Effort DBDCopy Defining DB2 columns as character eliminates the need for data cleansing and the need for FBE and IRD exits DBD Defining DB2 columns with a correct DB2 data type. This option exposes IMS data consistency and may require data cleansing and data transformation exits. CopyDBD Data re-engineering allows full control over the final result of the migration. Fields can be changed, columns added or deleted and data transformed. Segments can be combined into one table or split into multiple tables Copy IMS Segment Type DatCK DBD DB2 Table Key – Data migration approach NATIVESQLACCESS ApplicationtestingTime/Effort SEQ SCH SCHCB1SEQ CB2 CB3 SEQ SCH SCHCB1SEQ CB2 CB3 SEQ SCH SEQ SEQ SEQ SEQ SEQ SEQ SCH Pref KEY CB1 COL CB2 CB3 CB4 Char Date Char Int Dec VCHar KEY CB1 COL CB2 CB3 Char Date Char Int Decimal KEY Char Char Char Char Char CB1 COL CB2 CB3 KEY Col Field Col Char Char Char Char OPTION 1 OPTION 2 OPTION 3 OPTION 4 Based on : - IMS DBD fields - Copybooks Based on : - IMS DBD fields - Copybooks + DB2 data type + re-engineering Based on : - IMS DBD fields Based on : - IMS DBD fields - Copybooks + DB2 data type
- 19. • Future Programming Changes • IMS/DLI Continue to use existing without changing application code Create new DLI calls – use existing PSBs • SQL * Can replace DLI calls with SQL reading/updating DB2 tables directly Compile process will create program package that is separate from DL2 PSB driver package New SQL may be added and may be helpful for analytical style processing May allow elimination of some COBOL filtering code Future application programming 19
- 20. • SQL can be used to access data • DB2 built in functions can be used for analytical/decision support type processing • Average, Count, etc – Option 3 conversion • Faster database changes • Easier modeling, give various database models a try • Less COBOL coding to filter records, the records returned are the ones you want • Analysis tools help spot potential performance problems before production implementation Post migration with DL/2 20
- 21. • Sophisticated tuning tools available • Can test/develop queries in ad-hoc tools such a SPUFI without writing a COBOL program • Deliver requests for information using ad-hoc reporting tools much faster than writing a COBOL program • Over time, rewriting to native DB2/SQL maybe of benefit? Post migration with DL/2 contd 21
- 22. • Getting buy-in from the DBA team, application stakeholders and senior management is the key to success • Review the current status of your IMS support team • What is the timeline for IMS skills to depart the organization • What is your backup plan to ensure on-going support of your IMS environment • Review current IMS DB MLC and IMS Tools licensing costs • Those costs continue as long as you are still maintaining IMS DB – DL/2 is a one time perpetual license fee • Discuss with Application stakeholders the benefits of shifting data to a relational model in Db2 – Ease of on-going maintenance, easier access to data and opportunity to modernize applications. Developing the internal business case 22
- 23. • MLC and term license costs • Cost of IMS Software • Cost of Software to monitor IMS – BMC, Compuware, CA, IBM • Cost of Software to Backup, Recover, Reorganize, Validate • Personnel / Consultants • Staffing Shortages • Fewer and fewer developers and DBA’s with IMS Skills • Potential future reliance on 3rd party support • Consolidate to one z/OS DBMS • Simplify DBA support Factors to consider in ROI 23
- 24. • Finance • Insurance • Healthcare • Local and State Government • Manufacturing • Retail • All customers have gained significant fiscal and operational benefits by migrating to Db2 with DL/2 Hear first hand from Damon Anderson Director of Data Services at Anixter about their successful migration project http://www.syncsort.com/en/Resource- Center/Mainframe/Webcasts/IMS-to-DB2-Migration Over 100 projects completed globally 24
- 25. Typical Migration Project • Databases grouped by application/size/complexity for optimal testing • Primarily 3 main project phases: Database Group 1 Database Group 2 Database Group 3 TIME Database Group n Eliminate IMS Database mapping usually performed by Syncsort Map/migrate Application testing Production cutover 25
- 26. • Free of charge DBD and PSB review service • Proof of concept • Mapping and migration service • Onsite support for production cutover Syncsort Migration Services 26
- 27. • No application program changes are required • Lowest risk migration strategy – bite-sized chunks • Reduced costs through elimination of IMS DB and BMC tools licenses • Simplification of DBA support through DBMS convergence • Choice of migration methods to meet differing requirements • Simple, rapid method to reduce costs very quickly • More measured method to meet Db2 design objectives • A combination of both • Simple method first, measured method later • Minor JCL changes (which can be made in advance) Why the transparency approach? 27
- 28. Take the first step Please contact me if you would like to discuss how DL/2 could benefit your organization bbostridge@syncsort.com 201-746-7083 With over 20 years experience in IMS to DB2 migrations, I am very confident Syncsort can help you make the move to Db2 28