The Internet Archive hosts a version of the 1989 edition that can be borrowed digitally.

Sections on program-to-program transitions (LINK, XCTL), transient data control, and temporary storage control.

If you own a legal copy of the CICS Handbook by Kageyama and are willing to share its ISBN and publication year for archival purposes, please comment below. If you know of an official digital repository (e.g., from the Computer History Museum), share that resource to help fellow mainframers.

For the modern system programmer, acquiring this handbook—whether through a used bookstore or a legitimate inter-library loan scan—is an investment in your understanding of CICS at the metal level. It transforms you from someone who merely codes EXEC CICS READ to someone who truly comprehends the journey of a transaction from the terminal through the TCB, into the DSA, and back.

: Commands like LINK (calling a sub-program and expecting a return) and XCTL (transferring control to another program without returning) are essential for application flow.

Published by McGraw-Hill, the is not just another technical manual. While IBM’s official documentation tells you what a command does, Kageyama explains how to think about CICS.

| Kageyama Concept | Modern CICS Equivalent | Why It Matters | | :--- | :--- | :--- | | | QR TCB vs. Open TCB (L8) | Still critical for multi-threading and deadlock analysis. | | Terminal Control Table (TCT) | TCP/IP Service and Terminal resources | Understanding terminal mapping helps with 3270 emulation modernization. | | Program Control Table (PCT) | Program and Transaction definitions in CSD | Security and transaction routing logic remain identical. | | Storage Violation (ASRA) | Storage Protection Key mechanism | Modern CICS dumps still require ASRA analysis per Kageyama’s methods. |