Part I: z/OS Foundations for the COBOL Architect
"You can write COBOL for twenty years and never understand the system your code runs on. The architects who get the 2am calls — and fix the problem in twenty minutes — are the ones who know what happens below the PROCEDURE DIVISION."
What This Part Covers
Part I builds the operating system foundation that separates COBOL programmers from COBOL architects. These five chapters cover the z/OS knowledge that most COBOL developers acquire piecemeal over a decade of production incidents — if they acquire it at all.
You already know how to write COBOL programs. This part teaches you how z/OS runs them: how your program gets its memory, how the Language Environment bootstraps your code before the first COBOL statement executes, how datasets are managed at the SMS and catalog level, and how the Workload Manager decides which of the thousand jobs competing for resources gets CPU time right now.
This knowledge has practical, immediate value. Understanding virtual storage architecture means you can diagnose an 80A abend in minutes instead of hours. Understanding WLM means you can explain to management why moving your batch job to a different service class won't fix the performance problem — and what will. Understanding Language Environment internals means you can tune LE runtime options to prevent storage leaks that only manifest under production load.
Chapters in This Part
| Chapter | Title | Key Question |
|---|---|---|
| 1 | The z/OS Ecosystem | How does the operating system serve your COBOL program? |
| 2 | Virtual Storage Architecture | Why does your program abend with 80A, and what can you do about it? |
| 3 | Language Environment Internals | What happens between CALL and your first PROCEDURE DIVISION statement? |
| 4 | Dataset Management Deep Dive | How do catalogs, DFSMS, and SMS classes affect your program's I/O? |
| 5 | z/OS Workload Manager | How does WLM decide when your batch job runs? |
Progressive Project: Getting Started
In these five chapters, you'll establish the infrastructure foundation for your HA banking transaction processing system: defining the z/OS environment, sizing address spaces, specifying LE runtime options, designing the dataset naming and SMS class strategy, and setting up WLM service classes for online and batch workloads.
Prerequisites
Solid COBOL programming skills. JCL fundamentals. Basic understanding of z/OS (you know what a LPAR is, you've submitted jobs, you've used ISPF). If any of these are shaky, review the prerequisites self-assessment in the frontmatter.