Subprograms and CALL Statements

A COBOL subprogram is a separately compiled unit of PROCEDURE DIVISION logic that a calling program invokes with the CALL statement instead of duplicating code inline. The calling program issues CALL 'SUBPROG' USING param-1 param-2, control transfers to the subprogram's PROCEDURE DIVISION, and the subprogram runs until it hits GOBACK or EXIT PROGRAM, at which point control returns to the statement immediately after the CALL. This mirrors how mainframe shops decompose large batch systems, such as a payroll run, into validation, calculation, and reporting subprograms that can each be tested, compiled, and maintained independently.

A static CALL uses a literal program name, such as CALL 'CALCTAX', and the linkage editor resolves that reference at link-edit time, embedding the subprogram's address directly into the load module; this is fast at runtime but means the main program must be re-link-edited whenever the subprogram changes. A dynamic CALL uses a data item instead of a literal, such as CALL WS-PROGRAM-NAME USING ..., and the operating system resolves and loads the subprogram at execution time, which lets shops swap subprogram versions without relinking the caller. Dynamic calls stay resident until an explicit CANCEL statement releases the subprogram's storage and resets its internal state, including any WORKING-STORAGE values retained between calls.

The default passing mechanism, BY REFERENCE, passes the address of a WORKING-STORAGE item, so any change the subprogram makes to the corresponding LINKAGE SECTION item is visible back in the calling program the moment control returns; this is how a subprogram commonly returns a computed result or a status flag. BY CONTENT passes a copy of the data at the moment of the call, so the subprogram can freely modify its local copy without any risk of corrupting the caller's original value, which is useful for read-only inputs like a company-code filter. BY VALUE, available in COBOL 2002 and later and commonly used when calling non-COBOL routines through a C-style interface, passes a literal or numeric value directly rather than an address, and the receiving LINKAGE SECTION item's PICTURE clause must be compatible in type and size with what the caller sends.

COBOL supports nested subprograms, defined between an inner PROGRAM-ID and END PROGRAM inside an enclosing program's source, which can share the outer program's data items if those items are declared with the GLOBAL clause, avoiding the need to pass every value through USING. External subprograms, by contrast, are compiled as entirely separate load modules with their own independent WORKING-STORAGE, and the only way data crosses the boundary is through the LINKAGE SECTION parameters on the CALL and PROCEDURE DIVISION USING statements or through shared files and databases. Most enterprise COBOL shops favor external subprograms for reusable business logic, such as a date-validation routine called from dozens of programs, because they compile independently and can be unit tested and version-controlled in isolation from any single calling program.