Chapter 32 Further Reading: Modernization Strategy

Tier 1: Verified IBM Documentation

Modernization Strategy and Assessment

IBM Mainframe Application Modernization IBM documentation library covering modernization strategies, patterns, and tools specifically for z/OS environments. Includes guidance on API wrapping, code refactoring, and hybrid cloud integration for COBOL workloads. Available at: IBM Documentation (https://www.ibm.com/docs/en/cloud-paks/z-modernization)

IBM Application Discovery and Delivery Intelligence (ADDI) Documentation for IBM's automated application analysis tool. ADDI analyzes COBOL source code, copybooks, JCL, CICS CSD definitions, and DB2 objects to produce dependency graphs, complexity metrics, and impact analysis reports. This is the tool Sandra Chen's team used for the FBA portfolio assessment. Available at: IBM Documentation (https://www.ibm.com/docs/en/addi)

IBM z/OS Connect EE The API mediation layer that enables COBOL CICS and IMS transactions to be exposed as RESTful APIs with OpenAPI 3.0 specifications. Chapter 21 covered the technical details; this documentation covers enterprise deployment, security configuration, and performance tuning. Available at: IBM Documentation (https://www.ibm.com/docs/en/zos-connect)

IBM Wazi as a Service IBM's cloud-hosted z/OS development and test environment. Relevant to modernization because it provides a cloud-based COBOL development platform without requiring a physical mainframe — useful for training new developers and running test workloads. Available at: IBM Documentation (https://www.ibm.com/docs/en/wazi-aas)

Cost and Pricing

IBM Tailored Fit Pricing for z/OS IBM's alternative pricing model that moves away from traditional MIPS-based licensing. Understanding how pricing models have evolved is essential for accurate TCO analysis. Tailored Fit Pricing can significantly change the mainframe cost equation for organizations with variable workloads. Available at: IBM z Systems pricing documentation

IBM Z and Cloud Modernization Center IBM's online resource for mainframe modernization, including cost calculators, assessment tools, and customer case studies. Includes the "Application Modernization Field Guide" with practical patterns for each modernization strategy. Available at: https://www.ibm.com/z/modernization

Tier 2: Industry Publications and Analysis

Analyst Reports

Gartner: "Migrate, Modernize or Leave in Place — A Decision Framework for Mainframe Applications" Gartner's framework for mainframe modernization decisions, including their five-Rs model (Rehost, Refactor, Revise, Rebuild, Replace). Compare with the four-Rs framework in this chapter. Gartner's data on modernization project failure rates and cost overruns is particularly valuable. Access: Requires Gartner subscription. Check your organization's analyst access.

Forrester: "The Total Economic Impact of Mainframe Modernization" Forrester's methodology for calculating the full TCO of mainframe modernization, including hidden costs, risk-adjusted costs, and the opportunity cost framework. Their finding that 60-70% of rehost projects underestimate costs by 2-3x is cited in this chapter. Access: Requires Forrester subscription.

International Data Corporation (IDC): "Worldwide Mainframe Modernization Forecast" IDC's annual market sizing and forecast for mainframe modernization spending. Includes data on which strategies organizations are actually choosing (vs. what vendors recommend) and success rates by strategy type. Access: Requires IDC subscription.

Micro Focus / OpenText: "State of Mainframe Modernization" Annual survey of mainframe professionals on modernization priorities, strategies, and outcomes. Useful for benchmarking your organization's modernization maturity against industry peers. Note that Micro Focus (now part of OpenText) has a commercial interest in rehost/replatform strategies — read with appropriate awareness. Available at: OpenText/Micro Focus website (often ungated)

Case Studies and Post-Mortems

Queensland Health Payroll Case Study Multiple published analyses of the Queensland Health payroll system replacement failure ($1.25 billion remediation). The Queensland Auditor-General's reports provide detailed technical and governance analysis. Search for "Queensland Health Payroll System Commission of Inquiry" for the most authoritative source. Available at: Queensland Audit Office publications (public)

UK Universal Credit Programme The UK National Audit Office has published multiple reports on the Universal Credit programme's delays and cost overruns. These provide detailed analysis of what went wrong in a large-scale benefits system modernization. Relevant comparison to the FBA case study. Available at: UK National Audit Office (https://www.nao.org.uk/) — search "Universal Credit"

US Government Accountability Office (GAO): "Information Technology: Agencies Need to Develop Modernization Plans for Critical Legacy Systems" GAO report identifying the most critical legacy systems in the US federal government and analyzing modernization strategies. The report specifically discusses the risks of "rip and replace" approaches for mission-critical systems. Available at: GAO.gov (https://www.gao.gov/) — Report GAO-19-471

Tier 3: Books and Technical References

Modernization Strategy

"Modernizing Enterprise COBOL Applications" by Tom Taulli Overview of modernization approaches for COBOL applications, including code analysis, API wrapping, and cloud migration. Accessible introduction for readers new to modernization strategy.

"Strangler Fig Application" by Martin Fowler The original description of the strangler fig pattern for incremental legacy system replacement. This short article (available on martinfowler.com) is the foundational reference for Chapter 33's detailed treatment. Available at: https://martinfowler.com/bliki/StranglerFigApplication.html

"Working Effectively with Legacy Code" by Michael Feathers While not mainframe-specific, Feathers's techniques for making legacy code testable, introducing seams for change, and managing technical debt are directly applicable to COBOL modernization. His concept of "characterization tests" (tests that document existing behavior rather than verifying intended behavior) is particularly relevant to Sandra's approach at FBA.

"Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith" by Sam Newman Patterns for decomposing monolithic applications into services. While written from a Java/cloud perspective, the patterns — especially the strangler fig, branch by abstraction, and parallel run — apply directly to COBOL modernization. Carlos Vega's recommended reading for understanding why incremental beats big-bang.

"Technology Strategy Patterns: Architecture as Strategy" by Eben Hewitt Framework for making technology strategy decisions that align with business strategy. Relevant to the modernization decision framework in Section 32.4 and the TCO analysis in Section 32.5. Particularly useful for architects who need to present modernization recommendations to non-technical leadership.

Technical References

"Enterprise COBOL for z/OS: Programming Guide" IBM Publication SC27-1412. The definitive reference for the COBOL language features that modernization projects must understand: inter-program communication (CALL, CANCEL), the COBOL runtime environment, XML and JSON processing capabilities, and Unicode support. Understanding what Enterprise COBOL can already do prevents unnecessary rewrites. Available at: IBM Documentation — Enterprise COBOL library

"CICS TS for z/OS: API Reference" IBM Publication SC34-7684. The complete CICS API reference. Relevant to modernization because understanding CICS capabilities (channels, containers, web services, event processing) reveals what can be modernized within CICS rather than by replacing it. Available at: IBM Documentation — CICS library

"DB2 for z/OS: Managing Performance" IBM Publication SC28-4190. Performance management techniques for DB2 on z/OS. Relevant to TCO analysis because many modernization proposals assume cloud database performance will match DB2-on-z/OS performance. This reference provides the baseline metrics needed for honest comparison. Available at: IBM Documentation — DB2 library

Tier 4: Online Resources and Communities

Open Mainframe Project (Linux Foundation) The Linux Foundation's initiative for mainframe open-source collaboration. Hosts Zowe (the open-source z/OS DevOps framework), the COBOL Programming Course, and community resources for mainframe modernization. Available at: https://www.openmainframeproject.org/

Planet Mainframe Industry news and analysis focused on mainframe technology and modernization. Regular articles from practitioners and analysts. Good for staying current on modernization trends, vendor announcements, and customer case studies. Available at: https://planetmainframe.com/

Mainframe DEV (Broadcom Community) Technical community for mainframe developers. Includes forums, tutorials, and code examples for modernization tools and techniques. Broadcom (which acquired CA Technologies) has a significant portfolio of mainframe tools. Available at: https://community.broadcom.com/mainframedev/

IBM Z and LinuxONE Community IBM's developer community for z/OS and LinuxONE. Includes hands-on labs, learning paths, and sandbox environments for practicing COBOL modernization techniques including z/OS Connect API development and Zowe. Available at: https://community.ibm.com/community/user/ibmz-and-linuxone/

Chapter-Specific Cross-References

Topic Where to Look
z/OS strengths to preserve during modernization Chapter 1 (z/OS Ecosystem)
CICS as modernization integration point Chapter 13 (CICS Architecture)
APIs as modernization enabler Chapter 21 (API-First COBOL)
Strangler fig pattern in detail Chapter 33 (Strangler Fig)
Cloud deployment patterns for COBOL Chapter 34 (COBOL-to-Cloud)
AI-assisted code analysis and documentation Chapter 35 (AI-Assisted COBOL)
CI/CD pipelines for mainframe Chapter 36 (DevOps for Mainframe)
Hybrid architecture end-state Chapter 37 (Hybrid Architecture)
Full system architecture synthesis Chapter 38 (Capstone)
Knowledge transfer frameworks Chapter 40 (Knowledge Transfer)