Appendix K: Bibliography

This bibliography is organized into three tiers reflecting the nature and verifiability of each source. This structure is not about ranking quality — a Tier 2 source may contain insights more valuable than any Tier 1 manual. The tiers are about epistemic honesty: telling you exactly what kind of source each reference is.

Tier 1: Verified References

These are primary sources — IBM documentation, published books, and standards documents that can be independently verified. If you need to resolve a technical question definitively, start here.

IBM Enterprise COBOL Documentation

  1. IBM Enterprise COBOL for z/OS: Programming Guide, Version 6 Release 4. IBM Corporation. SC27-8714. The authoritative reference for Enterprise COBOL on z/OS. Covers compiler options, runtime behavior, interoperability with DB2/CICS/MQ, and COBOL language extensions specific to z/OS. Referenced throughout this book, particularly Chapters 1–5 and 12.

  2. IBM Enterprise COBOL for z/OS: Language Reference, Version 6 Release 4. IBM Corporation. SC27-8713. The complete language specification. When a colleague says "COBOL can't do that," this is where you prove them wrong (or, occasionally, right). Referenced in Appendix A.

  3. IBM Enterprise COBOL for z/OS: Migration Guide, Version 6 Release 4. IBM Corporation. GC27-8715. Critical for shops migrating from older COBOL compilers (VS COBOL II, COBOL for MVS). Chapter 32 references migration considerations.

  4. IBM Enterprise COBOL for z/OS: Performance Tuning Guide, Version 6 Release 4. IBM Corporation. SC27-8716. Compiler optimization levels, runtime tuning, and benchmark methodologies. Referenced in Chapters 3 and 26.

z/OS Operating System Documentation

  1. z/OS MVS JCL Reference. IBM Corporation. SA23-1385. The definitive JCL reference. If you write JCL for a living (and if you're reading this book, you do), this should be within arm's reach. Referenced throughout, particularly Chapters 4, 23, and Appendix B.

  2. z/OS MVS JCL User's Guide. IBM Corporation. SA23-1386. More narrative than the reference; useful for understanding why JCL works the way it does. Referenced in Chapters 1 and 23.

  3. z/OS MVS System Commands. IBM Corporation. SA38-0666. Console commands for z/OS operators and systems programmers. Referenced in Chapters 1, 5, and 27.

  4. z/OS MVS Initialization and Tuning Reference. IBM Corporation. SA23-1380. System parameters that affect COBOL program behavior: CSA sizing, MEMLIMIT defaults, initiator configuration. Referenced in Chapters 2 and 5.

  5. z/OS MVS Programming: Assembler Services Reference. IBM Corporation. SA23-1372. Understanding SVCs, PC routines, and cross-memory services at the system programming level. Referenced in Chapter 1.

  6. z/OS Language Environment Programming Guide. IBM Corporation. SA38-0682. The definitive reference for LE runtime options, condition handling, storage management, and enclave architecture. Chapter 3 is built on this manual. Referenced extensively in Chapters 3 and 18.

  7. z/OS Language Environment Programming Reference. IBM Corporation. SA38-0683. Callable services, macros, and control blocks. Referenced in Chapter 3.

  8. z/OS Language Environment Customization. IBM Corporation. SA38-0685. Installation-level LE configuration. How to set system-wide defaults for CEEDOPT, CEEUOPT, and CEEROPT. Referenced in Chapter 3.

  9. z/OS DFSMS: Using Data Sets. IBM Corporation. SC23-6855. VSAM internals, sequential dataset management, PDSE structure. The foundational reference for Chapter 4.

  10. z/OS DFSMS: Managing Catalogs. IBM Corporation. SC23-6853. ICF catalog architecture, alias resolution, GDG management. Referenced in Chapter 4.

  11. z/OS DFSMS: Storage Administration. IBM Corporation. SC23-6856. SMS class definitions, ACS routine coding, storage group management. Referenced in Chapter 4.

  12. z/OS MVS Planning: Workload Management. IBM Corporation. SA23-1390. WLM architecture, service definitions, classification rules. The technical foundation for Chapter 5.

  13. z/OS Security Server RACF Security Administrator's Guide. IBM Corporation. SA23-2289. RACF architecture, profile management, and security administration. The primary reference for Chapter 28.

  14. z/OS Security Server RACF Command Language Reference. IBM Corporation. SA23-2292. Every RACF command you'll ever need. Referenced in Chapter 28.

  15. z/OS Cryptographic Services: ICSF Administrator's Guide. IBM Corporation. SA22-7521. Key management, CPACF exploitation, and cryptographic services configuration. Referenced in Chapter 28.

  16. z/OS Communications Server: IP Configuration Guide. IBM Corporation. SC27-3650. TCP/IP configuration including AT-TLS for transport layer security. Referenced in Chapter 28.

DB2 for z/OS Documentation

  1. DB2 for z/OS: SQL Reference, Version 13. IBM Corporation. SC27-8855. The complete SQL syntax reference for DB2 on z/OS. Referenced throughout Part II (Chapters 6–12).

  2. DB2 for z/OS: Application Programming Guide and Reference for Java, Version 13. IBM Corporation. SC27-8854. While this book focuses on COBOL, the Java guide is relevant for modernization patterns where COBOL and Java coexist. Referenced in Chapters 33 and 34.

  3. DB2 for z/OS: Administration Guide, Version 13. IBM Corporation. SC27-8844. Database administration: tablespace design, buffer pool tuning, utility management, locking configuration. Referenced extensively in Chapters 6–9.

  4. DB2 for z/OS: Performance Monitoring and Tuning Guide, Version 13. IBM Corporation. SC27-8850. EXPLAIN interpretation, DSN_STATEMNT_TABLE analysis, accounting trace analysis. The technical foundation for Chapter 11.

  5. DB2 for z/OS: Utility Guide and Reference, Version 13. IBM Corporation. SC27-8856. REORG, RUNSTATS, COPY, RECOVER, LOAD — complete syntax and operational guidance. The primary reference for Chapter 9.

  6. DB2 for z/OS: Managing Security, Version 13. IBM Corporation. SC27-8849. DB2 security model: GRANT/REVOKE, DSNR RACF class, trusted contexts, row/column access control. Referenced in Chapters 12 and 28.

  7. DB2 for z/OS: Codes, Version 13. IBM Corporation. GC27-8847. SQLCODE and SQLSTATE reference. Keep this open during any DB2 debugging session. Referenced throughout Part II and Appendix D.

  8. DB2 for z/OS: Data Sharing: Planning and Administration, Version 13. IBM Corporation. SC27-8845. Coupling Facility structure sizing, lock protocol in data sharing, group buffer pool management. Referenced in Chapters 8 and 30.

CICS Documentation

  1. CICS Transaction Server for z/OS: Application Programming Reference, Version 5.6. IBM Corporation. SC34-7434. EXEC CICS command reference — the CICS equivalent of the COBOL Language Reference. Referenced throughout Part III (Chapters 13–18).

  2. CICS Transaction Server for z/OS: Application Programming Guide, Version 5.6. IBM Corporation. SC34-7432. Programming patterns, pseudo-conversational design, BMS, channels and containers. Referenced in Chapters 13–15.

  3. CICS Transaction Server for z/OS: System Programming Reference, Version 5.6. IBM Corporation. SC34-7436. Resource definition, system initialization parameters, and CEDA commands. Referenced in Chapters 13 and 17.

  4. CICS Transaction Server for z/OS: Performance Guide, Version 5.6. IBM Corporation. SC34-7438. MAXTASK sizing, DSA tuning, monitoring statistics interpretation. The primary reference for Chapter 17.

  5. CICS Transaction Server for z/OS: Recovery and Restart Guide, Version 5.6. IBM Corporation. SC34-7435. Journal management, XA recovery, indoubt resolution, emergency restart. Referenced in Chapter 18.

  6. CICS Transaction Server for z/OS: Internet Guide, Version 5.6. IBM Corporation. SC34-7433. Web services, REST APIs, PIPELINE configuration, JSON transformation. Referenced in Chapters 14 and 21.

  7. CICS Transaction Server for z/OS: CICSPlex SM Administration, Version 5.6. IBM Corporation. SC34-7430. CICSPlex SM topology, workload management, BAS deployment. Referenced in Chapter 13.

  8. CICS Transaction Server for z/OS: CICS and Liberty. IBM Corporation. SC34-7431. Liberty JVM server within CICS — relevant for modernization patterns. Referenced in Chapters 33 and 34.

IBM MQ Documentation

  1. IBM MQ for z/OS: Programming Guide. IBM Corporation. SC34-6982. MQI programming reference for COBOL on z/OS. The primary reference for Chapter 19.

  2. IBM MQ for z/OS: System Administration Guide. IBM Corporation. SC34-6980. Queue manager configuration, channel management, shared queue setup. Referenced in Chapters 19 and 20.

  3. IBM MQ for z/OS: Messages and Codes. IBM Corporation. SC34-6985. MQ reason codes and their meanings. Like DB2 codes, keep this open during debugging. Referenced in Chapter 19.

  4. IBM MQ: Designing and Planning. IBM Corporation. SC34-6977. Architecture guidance for MQ topology design, including clustering and shared queues. Referenced in Chapters 19 and 22.

IBM Redbooks

  1. ABCs of z/OS System Programming, Volumes 1–13. IBM Corporation. SG24-6981 through SG24-6990. The multi-volume series that explains z/OS system programming from fundamentals through advanced topics. Referenced in Chapters 1–5.

  2. DB2 for z/OS: Optimizer Internals and Tuning. IBM Corporation. SG24-8222. Deep dive into the DB2 optimizer's decision-making process. Referenced in Chapter 6.

  3. CICS Performance and Tuning: A Practical Guide. IBM Corporation. SG24-7074. Real-world CICS performance analysis and tuning techniques. Referenced in Chapter 17.

  4. IBM MQ: Design and Architecture. IBM Corporation. SG24-7MSO. MQ architecture patterns and best practices for z/OS environments. Referenced in Chapters 19–22.

  5. Parallel Sysplex: Architecture and Application Design. IBM Corporation. SG24-5765. How to design applications for Parallel Sysplex environments, including data sharing and workload distribution. Referenced in Chapters 1 and 30.

  6. z/OS Disaster Recovery: Architecture and Planning. IBM Corporation. SG24-6847. GDPS, Metro Mirror, XRC, and DR architecture patterns. The primary reference for Chapter 30.

  7. z/OS Security: Comprehensive Guide. IBM Corporation. SG24-7249. End-to-end z/OS security architecture: RACF, encryption, network security, audit. Referenced in Chapter 28.

  8. Batch Modernization: Patterns and Best Practices for the Mainframe. IBM Corporation. SG24-7779. Batch architecture optimization including parallel processing, checkpoint/restart, and scheduling. Referenced in Chapters 23–27.

  9. CICS and Liberty: Building Web Applications on z/OS. IBM Corporation. SG24-8418. Modern web application development within CICS, including REST APIs and microservice patterns. Referenced in Chapters 14, 21, 33.

  10. Modernizing Applications with IBM COBOL. IBM Corporation. SG24-8488. Modernization patterns for COBOL applications, including API enablement and hybrid architecture. Referenced in Part VII.

Canonical Textbooks

  1. Stern, Nancy B., Robert A. Stern, and James P. Ley. COBOL for the 21st Century, 11th Edition. John Wiley & Sons. The widely-used COBOL textbook. Books 1 and 2 of the DataField.Dev trilogy assume familiarity with material at this level.

  2. Murach, Mike, and Anne Prince. Murach's Mainframe COBOL. Mike Murach & Associates. Practical, example-driven COBOL instruction. A strong foundation text for readers coming to this book from the Murach series.

  3. Mullins, Craig S. DB2 Developer's Guide, 6th Edition. IBM Press / Pearson. Comprehensive DB2 application development reference. Particularly strong on EXPLAIN interpretation and performance tuning. Referenced in Chapters 6–12.

  4. Horswill, John, Ezriel Gross, and Rich Jackson. CICS: A Practical Guide to System Fine Tuning. Xephon (now IBM Systems Magazine). Classic CICS tuning reference. Referenced in Chapter 17.

  5. Date, C.J. An Introduction to Database Systems, 8th Edition. Addison-Wesley. The foundational database theory text. Locking, isolation levels, and transaction processing theory referenced in Chapter 8.

  6. Hohpe, Gregor, and Bobby Woolf. Enterprise Integration Patterns. Addison-Wesley. The canonical reference for messaging and integration patterns. Every pattern in Chapters 19–22 traces back to this book.

  7. Fowler, Martin. Patterns of Enterprise Application Architecture. Addison-Wesley. Architectural patterns referenced in Part VII, particularly the strangler fig pattern (Chapter 33).

  8. Newman, Sam. Building Microservices, 2nd Edition. O'Reilly Media. Referenced in Chapters 33 and 37 for decomposition strategies and the tension between microservices and monolithic COBOL.

  9. Kim, Gene, Jez Humble, Patrick Debois, and John Willis. The DevOps Handbook, 2nd Edition. IT Revolution Press. DevOps principles adapted for mainframe in Chapter 36.

  10. Forsyth, Dan, and Dennis Ng. Enterprise COBOL Programming. CreateSpace. Practical z/OS COBOL programming with emphasis on DB2 and CICS integration.

Standards and Regulations

  1. PCI Security Standards Council. Payment Card Industry Data Security Standard (PCI-DSS), Version 4.0. Referenced in Chapter 28 for cardholder data protection requirements.

  2. U.S. Department of Health and Human Services. HIPAA Security Rule: 45 CFR Parts 160, 162, and 164. Referenced in Chapter 28 for ePHI protection requirements.

  3. U.S. Congress. Sarbanes-Oxley Act of 2002 (SOX), Sections 302 and 404. Referenced in Chapter 28 for financial reporting controls and audit trail requirements.

  4. NIST (National Institute of Standards and Technology). NIST Cybersecurity Framework (CSF), Version 2.0. Referenced in Chapter 28 for security architecture assessment.

  5. NIST. FIPS 140-3: Security Requirements for Cryptographic Modules. Referenced in Chapter 28 for z/OS CPACF and ICSF compliance.

Tier 2: Attributed References

These references represent industry knowledge, community wisdom, and professional presentations that inform the guidance in this book. They may be harder to independently verify than Tier 1 sources, but they represent the collective experience of the mainframe community.

Industry Publications and Community Resources

  1. IBM Systems Magazine (z/OS edition). Various articles on z/OS performance, DB2 tuning, CICS architecture, and modernization strategies. Published continuously, now available at ibmsystemsmag.com. Referenced across multiple chapters.

  2. SHARE Inc. Presentations from the SHARE user group conferences (various years). SHARE is the oldest and largest IBM user group, and its presentations represent peer-reviewed (by practitioners) technical content. Specific topics referenced: DB2 optimizer internals (Sessions from IBM DB2 lab), CICS performance tuning (Sessions from IBM CICS development), batch window optimization (practitioner sessions). Referenced in Chapters 6, 17, 23.

  3. GUIDE Share Europe (GSE). Presentations from European user group conferences. Similar to SHARE, providing practitioner-level technical content. Referenced in Chapters 23 and 30.

  4. IBM Developer Community — Mainframe. Articles, tutorials, and code samples from IBM's developer community portal. Referenced for modernization topics in Part VII.

  5. Open Mainframe Project (Linux Foundation). Resources on Zowe, COBOL training, and mainframe open-source initiatives. Referenced in Chapters 35 and 36.

  6. Planet Mainframe. Industry news and technical articles on mainframe technology, workforce trends, and modernization. Referenced in Chapters 32 and 39.

  7. Compuware (now BMC) Technical Publications. Performance analysis methodology, Topaz/Strobe reference material, and DB2 tuning guidance. Referenced in Chapters 11 and 29.

  8. Broadcom (formerly CA Technologies) Documentation. CA-7 scheduling documentation, CA-1 tape management, and SYSVIEW performance monitoring. Referenced in Chapters 23 and 27.

  9. BMC Software Documentation. Control-M scheduling, MainView performance monitoring, and AMI operational automation. Referenced in Chapters 23, 27, and 31.

Workforce and Industry Research

  1. Deloitte Consulting. Mainframe Modernization: Bridging the Old and the New. Industry report on modernization strategies and workforce challenges. Referenced in Chapter 32.

  2. Micro Focus (now OpenText). The State of COBOL. Annual industry survey on COBOL usage, modernization trends, and workforce demographics. Referenced in Chapter 39.

  3. Kyndryl. Various publications on mainframe managed services, modernization, and hybrid cloud strategies. Referenced in Chapters 34 and 37.

  4. IBM Institute for Business Value. Mainframe in the Age of Hybrid Cloud. Research report on mainframe's role in hybrid cloud architectures. Referenced in Chapter 37.

Tier 3: Illustrative References

All case studies, production incidents, and character scenarios in this textbook are composite examples created for instructional purposes. They are clearly marked as such throughout the text.

Anchor Example Organizations

  1. Continental National Bank (CNB). Composite example inspired by the architecture patterns of large U.S. commercial banks. CNB's 500M transaction/day volume, 4-LPAR Parallel Sysplex, and DB2/CICS/MQ infrastructure represent a realistic Tier-1 bank architecture. No single real institution is depicted; the architecture is assembled from publicly documented patterns at multiple organizations. Referenced in all 40 chapters.

  2. Pinnacle Health Insurance. Composite example representing a mid-to-large health insurance company. The claims adjudication architecture, HIPAA compliance requirements, and batch processing volumes reflect industry-standard patterns for health payers. Referenced in Chapters 6, 10, 22–28.

  3. Federal Benefits Administration (FBA). Composite example representing a U.S. federal government agency with legacy IMS-based systems. The 40-year codebase, 15 million lines of COBOL, and modernization challenges reflect patterns common across multiple federal agencies. Referenced in Chapters 28, 30, 32–37, 40.

  4. SecureFirst Retail Bank. Composite example representing a mid-size bank pursuing digital transformation. The mobile-first modernization, strangler fig pattern, and CI/CD adoption represent patterns documented in multiple industry case studies. Referenced in Chapters 14, 21, 33–37.

Characters

  1. All characters in this textbook — Kwame Mensah, Lisa Tran, Rob Calloway, Diane Okoye, Ahmad Rashidi, Sandra Chen, Marcus Whitfield, Yuki Nakamura, Carlos Vega — are fictional composites. They represent recognizable archetypes in the mainframe profession: the veteran architect, the meticulous DBA, the operations disciplinarian, the bridge-builder, the compliance expert, the pragmatic modernizer, the retiring SME, the DevOps champion, and the distributed-world newcomer. No real individuals are depicted.

Production Incidents

  1. All production incidents described in this textbook (deadlock cascades, batch window overruns, access path regressions, security breaches, DR test failures) are composite scenarios assembled from patterns common to the mainframe industry. They are designed to be realistic and instructive. No specific real incident at any real organization is depicted.

How to Use This Bibliography

For technical accuracy: Start with Tier 1 IBM documentation. The manual numbers (SC27-xxxx, SA23-xxxx, GC27-xxxx, SG24-xxxx) are stable identifiers; even if URLs change, you can always find an IBM manual by its order number on the IBM Documentation website (ibm.com/docs).

For practical guidance: The Redbooks (SG24-xxxx) are particularly valuable because they bridge the gap between reference documentation and real-world practice. They're written by IBM lab engineers and experienced practitioners, and they include worked examples that the reference manuals lack.

For architectural patterns: The textbooks by Hohpe/Woolf, Fowler, and Newman provide the distributed-systems architectural vocabulary that mainframe architects need for hybrid and modernization work (Chapters 32–37).

For staying current: SHARE and GSE conference proceedings, IBM Systems Magazine, and the Open Mainframe Project are the best sources for keeping up with the evolving mainframe ecosystem. The mainframe community is smaller than the distributed systems community, but it is remarkably generous with its knowledge — attend a SHARE conference and you'll leave with more practical knowledge than any single book can provide.

A note on edition currency: Technology documentation is a moving target. The IBM manual numbers listed here are for the versions current at the time of writing. Always verify that you're reading the manual for the version of the product installed in your environment. A DB2 12 manual will mislead you if you're running DB2 13 — and vice versa.