Module layout 

WORKING-STORAGE as IBM lays it out: sizes by USAGE and PICTURE, REDEFINES sharing storage, OCCURS repeating it, SYNCHRONIZED slack bytes before an item and after each occurrence, and level-66 RENAMES over what is laid out. See numeric::assumptions::WORKING_STORAGE_LAYOUT for where each 01 level starts.

Structs

Condition

Item

Layout

Enums

Binding

Where a record addressed as a LINKAGE record is. Every other record is in the program’s own storage (Language Reference SC27-8713-03, pp. 63-66).

Kind

Resolved

Section

Where a GLOBAL record is in the program that declares it.

Constants

MAX_STORAGE

The interpreter’s ceiling on WORKING-STORAGE, well under Enterprise COBOL’s own.

Functions

build

Lays out WORKING-STORAGE, then each file’s record area, which all its 01 records share and which is at least record_max bytes. Files whose shared entry names the same file share one area, as large as the largest of them (see record_area_owners). notation is what SPECIAL-NAMES changes in the PICTUREs; qualify how RENAMES and later references resolve. Under PARMCHECK, parmcheck is how many of entries the program declares itself, the special registers the compiler adds following them, and the bytes of the buffer that goes between (Programming Guide SC27-8714-03, p. 397).

record_area_owners

The file whose record area each file uses: its own, or the first file of its SAME RECORD AREA clause. SAME AREA shares the record area of the VSAM (indexed and relative) files it names and is documentation for the rest: SAME_AREA_VSAM in numeric::assumptions.