COBOL / CORE CONCEPTS
Data names, levels, and working storage
Learn how data names, levels, and working storage works in COBOL, why the underlying model matters, and how to apply it in a small program without hiding important trade-offs.
What you will learn
- Explain data names in COBOL using the correct mental model
- Trace a focused COBOL example and predict its result before execution
- Recognize a boundary case involving levels and handle it deliberately
Understanding Data names, levels, and working storage
Data names, levels, and working storage belongs to the practical core of COBOL. Start by identifying the values or state involved and the rule that connects the input to the result.
Trace the example one operation at a time. Keep data names visible in the code rather than hiding it behind an abstraction before the behavior is understood.
Test a normal case and a boundary case. The difference between the prediction and the observed result is the most useful signal for deciding what to review next.
Data names, levels, and working storage is a defining part of practical COBOL work. Start by identifying the data or state involved, then trace the operation that changes or interprets it. Pay attention to the rules COBOL applies at this boundary, because those rules explain both the useful behavior and the common failure modes. This lesson keeps the example deliberately small, then connects it to picture clauses, groups, and numeric formats so the ideas form a coherent progression rather than a list of isolated syntax facts.
Worked examples
Data names, levels, and working storage example
A focused COBOL example for data names.
IDENTIFICATION DIVISION.
PROGRAM-ID. HELLO.
PROCEDURE DIVISION.
DISPLAY 'HELLO FROM COBOL'.
STOP RUN.
*> Lesson 3: data names. Change one value and predict the result before running it.Example explained
Line 1Identify where data names appears in the COBOL example and name the data it operates on.
Line 2Trace the relevant COBOL rule one operation at a time, recording any state, type, or control-flow change.
Line 3Change one input or boundary condition, predict the result, and compare that prediction with the documented outcome.
Important notes
Keep the first data names example small enough to trace completely.
Use the normal COBOL toolchain or browser workspace to compare the actual result with your prediction.
Common mistakes
Treating data names as punctuation to memorize instead of a COBOL behavior to reason about.
Ignoring levels until it appears in production data or a larger program.
Try it yourself
Change, predict, then run
Create a small COBOL example that demonstrates data names. Add a normal case and a boundary case, write down the expected result for each, then explain which COBOL rule produces that result. Lesson 3 should remain small enough to trace without guessing.
Open COBOL workspaceCheck your understanding
What is the best first step when working with data names?
- Identify the data and predict the result
- Add more abstraction immediately
- Ignore boundary cases
- Memorize punctuation only
Show answer
A clear input, operation, and predicted result create a testable mental model.