COBOL Programming: Beginner's Guide for Modern Developers

COBOL (Common Business Oriented Language) is one of the oldest programming languages still in active use, designed specifically for business data processing — and it still handles over 80% of the world’s business transactions from banking systems to airline reservations.

What You’ll Learn

• The four DIVISIONs of a COBOL program and what each does
• How to write and run your first COBOL program
• File handling with sequential file access
• Why COBOL remains critical in the age of cloud computing

Why COBOL Matters

Every time you check your bank balance, pay with a credit card, or book a flight, COBOL code is likely running behind the scenes. There are over 200 billion lines of COBOL code still in production, processing $3 trillion in daily transactions. Banks, insurance companies, and government agencies rely on COBOL programs written decades ago.

DodaZIP uses COBOL-inspired file record structures for processing compressed archives. Durga Antivirus Pro applies COBOL-style sequential scanning patterns to check files for malware signatures in order.

Learning Path

    flowchart LR
  A[Mainframe Basics] --> B[COBOL Programming<br/>You are here]
  B --> C[JCL Job Control]
  C --> D[CICS Transactions]
  D --> E[DB2 & IMS Databases]
  

What Is COBOL?

Think of COBOL as a language that let you write instructions in plain English. While other languages use symbols and cryptic syntax, COBOL reads almost like a sentence:

ADD 1 TO COUNTER.
MOVE "HELLO" TO MESSAGE.

This readability was intentional. COBOL was designed in 1959 for business users — accountants, managers, and clerks — not just programmers. They wanted a language where you could read the code and understand what it did without being a computer scientist.

The Four DIVISIONs

Every COBOL program is divided into exactly four sections, in order:

Analogy: DIVISIONs Are Like a Recipe

• IDENTIFICATION: The recipe name (“Grandma’s Cookies”)
• ENVIRONMENT: Which oven to use (gas, electric, temperature)
• DATA DIVISION: The ingredients list (flour, sugar, eggs) with quantities
• PROCEDURE DIVISION: The steps: mix, bake, cool, serve

Your First COBOL Program

Let’s write a program that displays a message. In COBOL, everything between column positions has meaning — a legacy from punch cards — but modern compilers accept free format.

       IDENTIFICATION DIVISION.
       PROGRAM-ID. HELLO-WORLD.
       AUTHOR. DODATECH.

       PROCEDURE DIVISION.
       MAIN-PARAGRAPH.
           DISPLAY "HELLO, COBOL!".
           STOP RUN.

Let’s break this down:

• IDENTIFICATION DIVISION: Tells the compiler the program’s name
• PROGRAM-ID: The specific name of this program — HELLO-WORLD
• PROCEDURE DIVISION: Where the executable code lives
• DISPLAY: Prints text to the screen (like echo in Bash or print() in Python)
• STOP RUN: Ends the program and returns control to the operating system

Expected output:

HELLO, COBOL!

Working with Variables

In COBOL, you must define every variable in the DATA DIVISION before using it. The language is statically typed — you must say exactly how much space each piece of data needs.

       DATA DIVISION.
       WORKING-STORAGE SECTION.
       01 WS-NAME      PIC X(30).
       01 WS-AGE       PIC 9(3).
       01 WS-BALANCE   PIC 9(7)V99.

       PROCEDURE DIVISION.
       MAIN.
           MOVE "ALICE" TO WS-NAME.
           MOVE 25 TO WS-AGE.
           MOVE 5000.50 TO WS-BALANCE.
           DISPLAY "NAME: " WS-NAME.
           DISPLAY "AGE: " WS-AGE.
           DISPLAY "BALANCE: $" WS-BALANCE.
           STOP RUN.

Line-by-line explanation:

• PIC X(30): A text field that holds up to 30 characters
• PIC 9(3): A numeric field that holds up to 3 digits (0-999)
• PIC 9(7)V99: A decimal number with 7 digits before the decimal and 2 digits after (total 9 digits)
• MOVE: Assign a value to a variable (like = in other languages)

Expected output:

NAME: ALICE
AGE: 025
BALANCE: $0005000.50

Notice the leading zeros. COBOL stores numbers with exact positions, so 025 is “25 with leading zero padding.” This is important for financial systems where alignment matters.

File Handling in COBOL

COBOL’s real power is file processing. Let’s read a file and display its contents.

       IDENTIFICATION DIVISION.
       PROGRAM-ID. READ-FILE.
       ENVIRONMENT DIVISION.
       INPUT-OUTPUT SECTION.
       FILE-CONTROL.
           SELECT CUSTOMER-FILE ASSIGN TO "CUSTOMERS.DAT"
               ORGANIZATION IS LINE SEQUENTIAL.

       DATA DIVISION.
       FILE SECTION.
       FD CUSTOMER-FILE.
       01 CUSTOMER-RECORD.
          05 CUST-ID      PIC 9(5).
          05 CUST-NAME    PIC X(25).
          05 CUST-BALANCE PIC 9(7)V99.

       WORKING-STORAGE SECTION.
       01 WS-EOF          PIC X(01) VALUE "N".

       PROCEDURE DIVISION.
       OPEN-FILE.
           OPEN INPUT CUSTOMER-FILE.

       READ-NEXT.
           READ CUSTOMER-FILE INTO CUSTOMER-RECORD
               AT END MOVE "Y" TO WS-EOF
           END-READ.
           IF WS-EOF = "N"
               DISPLAY CUST-ID " " CUST-NAME " $" CUST-BALANCE
               GO TO READ-NEXT
           END-IF.

       CLOSE-FILE.
           CLOSE CUSTOMER-FILE.
           STOP RUN.

Walkthrough:

• FILE-CONTROL: Connects the program to a physical file on disk
• FD (File Description): Defines the record layout of the file
• 05-level entries: Sub-fields within the record (like struct members)
• OPEN INPUT: Opens the file for reading
• READ … AT END: Reads a record; when there are no more records, sets an end-of-file flag
• GO TO: Jumps back to read the next record (old-school loop)

Assuming CUSTOMERS.DAT contains:

00001ALICE                   0005000.50
00002BOB                     0000250.00
00003CHARLIE                 0015000.00

Expected output:

00001 ALICE                      $0005000.50
00002 BOB                        $0000250.00
00003 CHARLIE                    $0015000.00

Why COBOL Still Runs the World

You might wonder: why don’t banks just rewrite everything in Python or Java?

Three reasons:

1. Risk: A COBOL payroll system that has processed paychecks without error for 40 years is not worth “fixing.” If a rewrite misses a single edge case, people don’t get paid.

2. Volume: 200+ billion lines of COBOL would take decades and billions of dollars to rewrite. Most organizations concluded it’s cheaper to maintain the old code.

3. Reliability: COBOL programs have been running for decades. They handle every edge case imaginable. Modern languages don’t have that proven track record.

Security Angle

COBOL’s fixed-length record structure actually provides a security benefit: buffer overflow attacks are much harder because field sizes are rigid. This is why mainframe security incidents are rare compared to cloud-based systems.

Durga Antivirus Pro uses COBOL-style fixed-record scanning for efficiently processing large numbers of files with predictable structures.

Common Mistakes

1. Forgetting periods in the right places

DISPLAY "Hello"   <- WRONG: missing period
DISPLAY "Hello".  <- CORRECT: ends the sentence

Periods end sentences in COBOL. Missing them causes compilation errors.

2. Confusing 01-level with subordinate levels

An 01-level defines a record. 05, 10, 15 levels define fields within that record. You cannot use MOVE on an 01-level the same way.

3. Thinking PIC 9(3) holds decimals

PIC 9(3) holds integers only (0-999). For decimals, use PIC 9(3)V9(2).

4. Not handling the AT END condition

If you read past the last record without checking AT END, your program abends (crashes).

5. Using GO TO excessively

GO TO creates “spaghetti code” that’s hard to maintain. Modern COBOL uses PERFORM (like functions) instead.

Practice Questions

1. What are the four COBOL DIVISIONs in order? IDENTIFICATION, ENVIRONMENT, DATA, PROCEDURE.

2. What does PIC 9(4)V99 mean? A numeric field with 4 digits before the decimal, 2 after — total 6 digits (e.g., 1234.56).

3. How do you read a file in COBOL? Use OPEN INPUT, then READ with AT END checking, then CLOSE when done.

4. What does STOP RUN do? Ends the program and returns control to the operating system or JCL job.

5. Why does COBOL use fixed-length fields? For predictable storage, memory alignment, and security — fixed lengths prevent buffer overflow attacks.

Challenge: Write a COBOL program that reads a file of employee records, calculates a 10% bonus for each employee, and displays the new salary. Use a PERFORM loop instead of GO TO.

FAQ

Try It Yourself

Install GnuCOBOL and run your first program:

# On Ubuntu/Debian
sudo apt-get install gnucobol

# Write and compile
cobc -x hello.cbl -o hello
./hello

Expected output:

HELLO, COBOL!

       IDENTIFICATION DIVISION.
       PROGRAM-ID. ADD-NUMBERS.
       DATA DIVISION.
       WORKING-STORAGE SECTION.
       01 WS-NUM1      PIC 9(3) VALUE 10.
       01 WS-NUM2      PIC 9(3) VALUE 20.
       01 WS-RESULT    PIC 9(4).

       PROCEDURE DIVISION.
       CALCULATE.
           COMPUTE WS-RESULT = WS-NUM1 + WS-NUM2.
           DISPLAY "THE SUM IS: " WS-RESULT.
           STOP RUN.

Expected output:

THE SUM IS: 0030

What’s Next

Built by the developers of Doda Browser, DodaZIP, and Durga Antivirus Pro. Updated 2026-06-06.

What’s Next

Congratulations on completing this Cobol tutorial! Here’s where to go from here:

• Practice daily — Consistency is more important than long study sessions
• Build a project — Apply what you learned by building something real
• Explore related topics — Check out other tutorials in the same category
• Join the community — Discuss with other learners and share your progress

Remember: every expert was once a beginner. Keep coding!