Further Reading: COBOL Program Structure Deep Dive

Official Language References

  • IBM Enterprise COBOL for z/OS: Language Reference (SC27-1408) — The definitive reference for COBOL syntax on IBM mainframes. The IDENTIFICATION DIVISION, ENVIRONMENT DIVISION, DATA DIVISION, and PROCEDURE DIVISION chapters map directly to this chapter's content. Available free from IBM Documentation.

  • ISO/IEC 1989:2023 — The official COBOL language standard. Expensive to obtain from ISO, but draft versions circulate in the standards community. Useful for understanding the "canonical" language definition versus vendor extensions.

  • GnuCOBOL Programmer's Guide — Covers GnuCOBOL-specific behavior for all four divisions, including areas where GnuCOBOL differs from Enterprise COBOL. Essential reference for Student Mainframe Lab users.

Books on COBOL Structure and Style

  • Murach, M. Murach's Mainframe COBOL. Mike Murach & Associates. Excellent coverage of program structure with a practical, IBM-centric perspective. The coding standards in Murach align closely with industry practice.

  • Stern, N., Stern, R., & Ley, J. COBOL for the 21st Century (11th edition). Wiley. Chapters on program structure provide a complementary perspective to this textbook, with different emphasis and examples.

  • Newcomer, L. IBM Mainframe COBOL: Getting the Most from Enterprise COBOL. Focused on Enterprise COBOL features that maximize performance and maintainability.

Coding Standards and Best Practices

  • IBM Enterprise COBOL: Best Practices — IBM Redpaper or Redbook (search IBM Redbooks for "COBOL best practices"). Provides IBM's own recommendations for program structure, coding standards, and performance.

  • Micro Focus COBOL Coding Standards Guide — Available from OpenText (formerly Micro Focus). Provides coding standards for Micro Focus environments but applicable broadly.

  • Open Mainframe Project: COBOL Check — An open-source unit testing framework for COBOL that encourages structured, testable program design. Understanding testing frameworks reinforces good structural practices.

Copybook Management

  • IBM SCLM (Software Configuration and Library Manager) — Documentation for IBM's mainframe library management tool, which handles copybook versioning and dependency tracking.

  • Changeman / Endeavor / ISPW — Commercial mainframe change management tools that include copybook impact analysis. Understanding these tools helps contextualize the copybook management challenges discussed in this chapter.

Historical and Conceptual

  • Dijkstra, E.W. "Go To Statement Considered Harmful" (1968). The famous paper that inspired COBOL's move toward structured programming in the COBOL-85 standard.

  • CODASYL COBOL Committee Documents — Historical documents from the committee that designed COBOL. Available in various archives. Fascinating for understanding why COBOL's structure was designed the way it was.

Online Resources

  • IBM COBOL Cafe — IBM's community forum for COBOL developers. Discussions often touch on program structure, coding standards, and best practices.

  • Stack Overflow [cobol] tag — Active community of COBOL developers answering questions. Search for questions about program structure, copybooks, and column conventions for practical guidance.