The COBOL core

The core is the whole of the business logic and nothing else: no files to find, no arguments to parse, no HTTP. It reads thirty-byte requests from standard input, writes fifty-byte answers to standard output, and returns a status that says whether anything was rejected. The Python service on the next page is the only program that starts it.

The core program

The file holds two programs. PRICE is the command: it opens /dev/stdin as a line sequential file, calls the unit for each record and displays the answer. PRICECORE is the unit: it validates the request, computes the net and the tax and fills the answer. The two records are written out here inside each program; the shipped file copies priceif.cpy of the previous page instead, and both forms were built and give the same output.

IDENTIFICATION DIVISION. PROGRAM-ID. PRICE. ENVIRONMENT DIVISION. INPUT-OUTPUT SECTION. FILE-CONTROL. SELECT REQ-F ASSIGN TO "/dev/stdin" ORGANIZATION IS LINE SEQUENTIAL FILE STATUS IS WS-REQ-STATUS. DATA DIVISION. FILE SECTION. FD REQ-F. 01 REQ-LINE PIC X(30). WORKING-STORAGE SECTION. 01 WS-REQ-STATUS PIC XX. 01 WS-EOF PIC X VALUE "N". 01 WS-COUNT PIC 9(3) VALUE 0. 01 WS-REJECTED PIC 9(3) VALUE 0. 01 PRICE-REQUEST. 05 PR-ORDER-ID PIC X(6). 05 PR-SKU PIC X(8). 05 PR-QTY PIC 9(5). 05 PR-CENTS PIC 9(9). 05 PR-REGION PIC X(2). 01 PRICE-ANSWER. 05 PA-ORDER-ID PIC X(6). 05 PA-STATUS PIC 9(2). 05 PA-NET PIC 9(11). 05 PA-TAX PIC 9(11). 05 PA-MESSAGE PIC X(20). PROCEDURE DIVISION. MAIN-PARA. OPEN INPUT REQ-F IF WS-REQ-STATUS NOT = "00" DISPLAY "core: cannot read the request stream" UPON STDERR MOVE 8 TO RETURN-CODE STOP RUN END-IF PERFORM UNTIL WS-EOF = "Y" READ REQ-F AT END MOVE "Y" TO WS-EOF NOT AT END PERFORM HANDLE-REQUEST END-READ END-PERFORM CLOSE REQ-F IF WS-COUNT = 0 MOVE 8 TO RETURN-CODE ELSE IF WS-REJECTED IS GREATER THAN 0 MOVE 4 TO RETURN-CODE END-IF END-IF STOP RUN. HANDLE-REQUEST. ADD 1 TO WS-COUNT MOVE REQ-LINE(1:6) TO PR-ORDER-ID MOVE REQ-LINE(7:8) TO PR-SKU MOVE REQ-LINE(15:5) TO PR-QTY MOVE REQ-LINE(20:9) TO PR-CENTS MOVE REQ-LINE(29:2) TO PR-REGION CALL "PRICECORE" USING PRICE-REQUEST PRICE-ANSWER IF PA-STATUS NOT = 0 ADD 1 TO WS-REJECTED END-IF DISPLAY PRICE-ANSWER. END PROGRAM PRICE. IDENTIFICATION DIVISION. PROGRAM-ID. PRICECORE. DATA DIVISION. LINKAGE SECTION. 01 PRICE-REQUEST. 05 PR-ORDER-ID PIC X(6). 05 PR-SKU PIC X(8). 05 PR-QTY PIC 9(5). 05 PR-CENTS PIC 9(9). 05 PR-REGION PIC X(2). 01 PRICE-ANSWER. 05 PA-ORDER-ID PIC X(6). 05 PA-STATUS PIC 9(2). 05 PA-NET PIC 9(11). 05 PA-TAX PIC 9(11). 05 PA-MESSAGE PIC X(20). PROCEDURE DIVISION USING PRICE-REQUEST PRICE-ANSWER. MOVE PR-ORDER-ID TO PA-ORDER-ID MOVE 0 TO PA-STATUS MOVE 0 TO PA-NET MOVE 0 TO PA-TAX MOVE SPACES TO PA-MESSAGE IF PR-SKU = SPACES MOVE 12 TO PA-STATUS MOVE "SKU IS EMPTY" TO PA-MESSAGE ELSE IF PR-QTY = 0 MOVE 4 TO PA-STATUS MOVE "QUANTITY IS ZERO" TO PA-MESSAGE ELSE EVALUATE PR-REGION WHEN "N1" CONTINUE WHEN "S2" CONTINUE WHEN "E3" CONTINUE WHEN "W4" CONTINUE WHEN OTHER MOVE 8 TO PA-STATUS MOVE "UNKNOWN REGION" TO PA-MESSAGE END-EVALUATE END-IF END-IF IF PA-STATUS = 0 COMPUTE PA-NET = PR-QTY * PR-CENTS COMPUTE PA-TAX ROUNDED = PA-NET * 13 / 100 MOVE "PRICED" TO PA-MESSAGE END-IF GOBACK. END PROGRAM PRICECORE.

Four details carry the design. The input is /dev/stdin in the ASSIGN clause, so the runtime reads the pipe the parent gave it and no temporary file exists anywhere. The answer is written with DISPLAY of the group, which prints its fifty bytes in order. The status field is reset at the top of every record, which is the bug that a first version of this page had: a program that forgets leaves the previous answer\'s status and rejects a good order with the last order\'s message. And PRICECORE is a separate program, so the same logic can be built as a module and called through ctypes without a process, which is the page after the tests.

The run

Five requests, one of each kind: a good one, a zero quantity, a region that is not one of the four, an empty SKU, and a second good one so that the status reset is visible:

C00001WIDGET0100002000123456N1 C00002WIDGET0200000000100000N1 C00003WIDGET0300001000100000X9 C00004 00003000001000S2 C00005WIDGET0500003000009999W4

cobc -x -free -Wall -O2 -o price price.cob
./price < requests.fixed
echo $?

C00001000000024691200000032099PRICED              
C00002040000000000000000000000QUANTITY IS ZERO    
C00003080000000000000000000000UNKNOWN REGION      
C00004120000000000000000000000SKU IS EMPTY        
C00005000000002999700000003900PRICED              
4

Each line is exactly fifty bytes and the message is padded to twenty with spaces, so the fixed-width answer survives a pipe and a log without a parser guessing where a field ends. The first order is two at 1234.56, which is 2469.12 net and 320.99 tax after ROUNDED; the last is three at 99.99, 299.97 and 38.99.

The exit status

Three numbers and each one is a case the service maps to HTTP: 0 when every request was priced, 4 when at least one was rejected, and 8 when the stream was empty, which usually means the caller sent nothing:

./price < /dev/null
echo $?

8

The rejected orders are still answered: the run above printed five lines and returned 4. A core that exited at the first bad order would leave the rest of a batch unpriced for one typo, which is the same argument the ledger capstone makes about postings.

The COBOL test driver

The core has a test driver in the style of the testing group: a table of five requests with the status, net and tax each must produce, a loop that calls PRICECORE, and a status of 1 if any case fails. The driver carries the unit in the same file, so it builds and runs on its own:

IDENTIFICATION DIVISION. PROGRAM-ID. CORETEST. DATA DIVISION. WORKING-STORAGE SECTION. 01 WS-CASES. 05 WS-CASE OCCURS 5 TIMES. 10 C-ID PIC X(6). 10 C-SKU PIC X(8). 10 C-QTY PIC 9(5). 10 C-CENTS PIC 9(9). 10 C-REGION PIC X(2). 10 C-EXPECT-STATUS PIC 9(2). 10 C-EXPECT-NET PIC 9(11). 10 C-EXPECT-TAX PIC 9(11). 01 WS-I PIC 9. 01 WS-PASSED PIC 9(3) VALUE 0. 01 WS-FAILED PIC 9(3) VALUE 0. 01 PRICE-REQUEST. 05 PR-ORDER-ID PIC X(6). 05 PR-SKU PIC X(8). 05 PR-QTY PIC 9(5). 05 PR-CENTS PIC 9(9). 05 PR-REGION PIC X(2). 01 PRICE-ANSWER. 05 PA-ORDER-ID PIC X(6). 05 PA-STATUS PIC 9(2). 05 PA-NET PIC 9(11). 05 PA-TAX PIC 9(11). 05 PA-MESSAGE PIC X(20). PROCEDURE DIVISION. MAIN-PARA. PERFORM FILL-CASES PERFORM VARYING WS-I FROM 1 BY 1 UNTIL WS-I > 5 PERFORM RUN-CASE END-PERFORM DISPLAY "passed " WS-PASSED " failed " WS-FAILED IF WS-FAILED IS GREATER THAN 0 MOVE 1 TO RETURN-CODE END-IF STOP RUN. FILL-CASES. MOVE "C00001" TO C-ID(1) MOVE "WIDGET01" TO C-SKU(1) MOVE 2 TO C-QTY(1) MOVE 123456 TO C-CENTS(1) MOVE "N1" TO C-REGION(1) MOVE 0 TO C-EXPECT-STATUS(1) MOVE 246912 TO C-EXPECT-NET(1) MOVE 32099 TO C-EXPECT-TAX(1) MOVE "C00002" TO C-ID(2) MOVE "WIDGET02" TO C-SKU(2) MOVE 0 TO C-QTY(2) MOVE 100000 TO C-CENTS(2) MOVE "N1" TO C-REGION(2) MOVE 4 TO C-EXPECT-STATUS(2) MOVE 0 TO C-EXPECT-NET(2) MOVE 0 TO C-EXPECT-TAX(2) MOVE "C00003" TO C-ID(3) MOVE "WIDGET03" TO C-SKU(3) MOVE 1 TO C-QTY(3) MOVE 100000 TO C-CENTS(3) MOVE "X9" TO C-REGION(3) MOVE 8 TO C-EXPECT-STATUS(3) MOVE 0 TO C-EXPECT-NET(3) MOVE 0 TO C-EXPECT-TAX(3) MOVE "C00004" TO C-ID(4) MOVE SPACES TO C-SKU(4) MOVE 3 TO C-QTY(4) MOVE 1000 TO C-CENTS(4) MOVE "S2" TO C-REGION(4) MOVE 12 TO C-EXPECT-STATUS(4) MOVE 0 TO C-EXPECT-NET(4) MOVE 0 TO C-EXPECT-TAX(4) MOVE "C00005" TO C-ID(5) MOVE "WIDGET05" TO C-SKU(5) MOVE 3 TO C-QTY(5) MOVE 9999 TO C-CENTS(5) MOVE "W4" TO C-REGION(5) MOVE 0 TO C-EXPECT-STATUS(5) MOVE 29997 TO C-EXPECT-NET(5) MOVE 3900 TO C-EXPECT-TAX(5). RUN-CASE. MOVE C-ID(WS-I) TO PR-ORDER-ID MOVE C-SKU(WS-I) TO PR-SKU MOVE C-QTY(WS-I) TO PR-QTY MOVE C-CENTS(WS-I) TO PR-CENTS MOVE C-REGION(WS-I) TO PR-REGION CALL "PRICECORE" USING PRICE-REQUEST PRICE-ANSWER IF PA-STATUS NOT = C-EXPECT-STATUS(WS-I) PERFORM FAIL-CASE ELSE IF PA-NET NOT = C-EXPECT-NET(WS-I) OR PA-TAX NOT = C-EXPECT-TAX(WS-I) PERFORM FAIL-CASE ELSE ADD 1 TO WS-PASSED DISPLAY "pass case " WS-I END-IF END-IF. FAIL-CASE. ADD 1 TO WS-FAILED DISPLAY "FAIL case " WS-I " status " PA-STATUS " net " PA-NET " tax " PA-TAX " expected " C-EXPECT-STATUS(WS-I) " " C-EXPECT-NET(WS-I) " " C-EXPECT-TAX(WS-I). IDENTIFICATION DIVISION. PROGRAM-ID. PRICECORE. DATA DIVISION. LINKAGE SECTION. 01 PRICE-REQUEST. 05 PR-ORDER-ID PIC X(6). 05 PR-SKU PIC X(8). 05 PR-QTY PIC 9(5). 05 PR-CENTS PIC 9(9). 05 PR-REGION PIC X(2). 01 PRICE-ANSWER. 05 PA-ORDER-ID PIC X(6). 05 PA-STATUS PIC 9(2). 05 PA-NET PIC 9(11). 05 PA-TAX PIC 9(11). 05 PA-MESSAGE PIC X(20). PROCEDURE DIVISION USING PRICE-REQUEST PRICE-ANSWER. MOVE PR-ORDER-ID TO PA-ORDER-ID MOVE 0 TO PA-STATUS MOVE 0 TO PA-NET MOVE 0 TO PA-TAX MOVE SPACES TO PA-MESSAGE IF PR-SKU = SPACES MOVE 12 TO PA-STATUS MOVE "SKU IS EMPTY" TO PA-MESSAGE ELSE IF PR-QTY = 0 MOVE 4 TO PA-STATUS MOVE "QUANTITY IS ZERO" TO PA-MESSAGE ELSE EVALUATE PR-REGION WHEN "N1" CONTINUE WHEN "S2" CONTINUE WHEN "E3" CONTINUE WHEN "W4" CONTINUE WHEN OTHER MOVE 8 TO PA-STATUS MOVE "UNKNOWN REGION" TO PA-MESSAGE END-EVALUATE END-IF END-IF IF PA-STATUS = 0 COMPUTE PA-NET = PR-QTY * PR-CENTS COMPUTE PA-TAX ROUNDED = PA-NET * 13 / 100 MOVE "PRICED" TO PA-MESSAGE END-IF GOBACK. END PROGRAM PRICECORE.

cobc -x -free -Wall -O2 -o coretest coretest.cob
./coretest
echo $?

pass case 1
pass case 2
pass case 3
pass case 4
pass case 5
passed 005 failed 000
0

The driver that fails

One expected value changed by a cent is enough to see the other branch, and it is the change a rounding bug makes:

sed 's/MOVE 246912 TO C-EXPECT-NET(1)/MOVE 246913 TO C-EXPECT-NET(1)/' \
    coretest.cob > coretest_bad.cob
sed -i 's/PROGRAM-ID. CORETEST./PROGRAM-ID. CORETESB./; s/END PROGRAM CORETEST./END PROGRAM CORETESB./' \
    coretest_bad.cob
cobc -x -free -Wall -O2 -o coretest_bad coretest_bad.cob
./coretest_bad
echo $?

FAIL case 1 status 00 net 00000246912 tax 00000032099 expected 00 00000246913 00000032099
pass case 2
pass case 3
pass case 4
pass case 5
passed 004 failed 001
1

The next page is the reason the core speaks on stdin: a Python service starts it once per request, maps its three exit statuses to HTTP, and gives the client fifty bytes or a JSON document.

The COBOL was built with cobc (GnuCOBOL) 3.2.0 with -O2 and run on Alpine Linux 3.24.3 (x86_64) in a Docker container with nproc 4 and Python 3.14.10.

Article author: Arthur Isaev