VALUE and Initial Contents

When you declare a variable in COBOL’s WORKING-STORAGE SECTION, you ask the computer for a specific chunk of memory. But what’s actually inside that memory when the program starts?

If you don’t explicitly tell COBOL what to put there, the answer is garbage.

       IDENTIFICATION DIVISION.
       PROGRAM-ID. SAFE-INIT.
       DATA DIVISION.
       WORKING-STORAGE SECTION.
       01 CLEAN-NUMBER PIC 9(3) VALUE 42.
       PROCEDURE DIVISION.
           DISPLAY CLEAN-NUMBER.
           STOP RUN.

042

The Danger of Raw Memory

In modern languages like Python or JavaScript, a new variable is automatically initialized to a clean state like undefined, null, or 0. A modern programmer intuitively expects “uninitialized” to mean “empty”.

That intuition fails in COBOL because the runtime does not garbage-collect or zero-out RAM when allocating variables. “Empty” literally means whatever random bits of data were left behind in that physical memory address by the last program that used it.

Why did the language designers build it this way? In the 1960s, wasting CPU cycles automatically zeroing out memory was considered too expensive, especially if the program was just going to immediately overwrite that memory by reading a record from a magnetic tape anyway. Performance was paramount, so the OS just handed you the raw bytes.

If you attempt to perform math on this garbage data, your program will crash or produce silent, incorrect calculations.

The Boundary: FILE and LINKAGE SECTION

The danger of raw, uninitialized memory only applies to the WORKING-STORAGE SECTION (which actually allocates new memory). In the FILE SECTION (reading from disk) and the LINKAGE SECTION (receiving parameters from another program), COBOL actually ignores the VALUE clause completely. Those sections don’t allocate new memory; they just map your variable names onto existing buffers that already contain data.

Attempting to perform math on garbage data will cause your program to crash or produce silent, incorrect calculations.

The VALUE Clause

To safely initialize a variable when the program loads, use the VALUE clause.

       IDENTIFICATION DIVISION.
       PROGRAM-ID. VAL-NUM.
       
       DATA DIVISION.
       WORKING-STORAGE SECTION.
       01 SCORE PIC 9(3) VALUE 100.
       01 GREETING PIC X(5) VALUE 'HELLO'.
       
       PROCEDURE DIVISION.
           DISPLAY "Score is: " SCORE.
           DISPLAY "Greeting is: " GREETING.
           STOP RUN.

Score is: 100
Greeting is: HELLO

Figurative Constants

COBOL has built-in keywords called figurative constants that represent common data patterns. They automatically scale to match the size of your PIC clause, so you don’t have to type out long strings of identical characters.

• ZEROS (or ZERO, ZEROES): Fills numeric fields with zeros.
• SPACES (or SPACE): Fills alphanumeric fields with blank spaces.

       IDENTIFICATION DIVISION.
       PROGRAM-ID. FIG-CONSTS.
       
       DATA DIVISION.
       WORKING-STORAGE SECTION.
       01 BLANK-SCORE PIC 9(3) VALUE ZEROS.
       01 BLANK-NAME PIC X(10) VALUE SPACES.
       
       PROCEDURE DIVISION.
           DISPLAY "Score: " BLANK-SCORE.
           DISPLAY "Name: [" BLANK-NAME "]".
           STOP RUN.

Score: 000
Name: [          ]

The INITIALIZE Verb

The VALUE clause only works exactly once: when the program is first loaded into memory. If you want to reset a variable back to a blank state during the execution of your program, you must use the INITIALIZE verb in the PROCEDURE DIVISION.

INITIALIZE wipes a data item clean, safely resetting it to its default state: spaces for alphanumeric variables, and zeros for numeric variables.

       IDENTIFICATION DIVISION.
       PROGRAM-ID. INIT-DEMO.
       
       DATA DIVISION.
       WORKING-STORAGE SECTION.
       01 MY-SCORE PIC 9(3) VALUE 500.
       01 MY-NAME  PIC X(5)  VALUE 'ALICE'.
       
       PROCEDURE DIVISION.
           DISPLAY "Before: " MY-NAME " " MY-SCORE.
           
           INITIALIZE MY-NAME.
           INITIALIZE MY-SCORE.
           
           DISPLAY "After: [" MY-NAME "] " MY-SCORE.
           STOP RUN.

Before: ALICE 500
After: [     ] 000

If you INITIALIZE a group item (a record containing multiple sub-variables), COBOL is smart enough to reset the numbers to 0 and the strings to spaces automatically!