COBOL 60

COBOL 60
Name	COBOL 60
Paradigm	Imperative, procedural
Designer	Grace Hopper, Committee members
Developer	CODASYL, U.S. Department of Defense
First appeared	1960
Typing	Static, strong
Influenced by	FORTRAN, FLOW-MATIC, AIMACO
Influenced	COBOL, PL/I

COBOL 60

COBOL 60 was the inaugural specification for a business-oriented programming language formalized in 1960. It emerged from collaboration among influential figures and institutions such as Grace Hopper, J. Presper Eckert, Remington Rand, Sperry Corporation, and Department of Defense (United States), aiming to support data processing needs of organizations like IBM, UNIVAC, General Electric, Bank of America, and AT&T. The specification set foundations relied upon precedents including FORTRAN, FLOW-MATIC, AIMACO, Bureau of the Budget (United States), and committees that later connected with CODASYL and ACM.

Overview

COBOL 60 defined a verbose, English-like syntax for business applications and record processing used by institutions such as Internal Revenue Service, Social Security Administration (United States), General Motors, Sears, Roebuck and Co., and Chase Manhattan Bank. Its design emphasized readability for managers in organizations like U.S. Navy, U.S. Air Force, U.S. Army, Harvard University, and MIT. The language specified divisions and paragraphs influenced by earlier work at Remington Rand, Burroughs Corporation, Honeywell, Control Data Corporation, and CDC to facilitate portability across hardware platforms produced by IBM, UNIVAC, and RCA.

History and Development

Development of COBOL 60 involved figures and entities including Grace Hopper, Howard Bromberg, Harry Huskey, Seymour Cray, Howard Aiken, J. Presper Eckert, and agencies like Department of Defense (United States), U.S. General Accounting Office, U.S. Bureau of the Budget (United States), and corporations such as IBM, Honeywell, Burroughs Corporation, Sperry Corporation, and Remington Rand. Early meetings took place alongside conferences involving Association for Computing Machinery, Institute of Electrical and Electronics Engineers, American National Standards Institute, and the Conference on Data Systems Languages founders. Proposals drew on prior languages and projects at Naval Ordnance Laboratory, RAND Corporation, MITRE Corporation, and Lockheed Martin research groups. The 1960 specification was an outcome of consensus among private firms and government offices like U.S. Department of Commerce, Treasury Department (United States), and private banking institutions including Wells Fargo.

Language Features and Syntax

COBOL 60 specified divisions such as IDENTIFICATION, ENVIRONMENT, DATA, and PROCEDURE influenced by structured documents used at Bell Labs, RAND Corporation, Sylvania Electric Products, and Western Electric. Data description features borrowed concepts from FORTRAN arrays and FLOW-MATIC records developed under teams at Remington Rand and Sperry Corporation. Syntax choices reflect input/output models used by IBM System/360 contemporaries and file-handling approaches adopted by UNIVAC I operations at U.S. Census Bureau installations. The language emphasized fixed-format source layouts similar to conventions in Harvard Mark I and paperwork practices in Federal Reserve System data centers. Numeric picture clauses, group items, and level numbers paralleled data modeling practices from Bank of America and Prudential Financial data shops.

Standardization and COBOL 60 Committee

Standardization activities around the 1960 specification involved organizations such as CODASYL, American National Standards Institute, Conference on Data Systems Languages, Association for Computing Machinery, Institute of Electrical and Electronics Engineers, Department of Defense (United States), and international bodies like International Organization for Standardization. The COBOL 60 Committee convened representatives from IBM, Honeywell, Burroughs Corporation, Sperry Corporation, Remington Rand, Naval Research Laboratory, National Security Agency, and U.S. General Services Administration. Debates over features included input from corporate delegations like General Electric and AT&T, academic participants from MIT, Stanford University, University of California, Berkeley, and regulatory observers from U.S. Congress budgetary staff. The committee’s work prefigured later standards and revisions that engaged ISO processes and national standards boards.

Implementations and Compilers

Early compilers and implementations were produced for hardware by IBM, UNIVAC, Remington Rand, Burroughs Corporation, Honeywell, and Control Data Corporation. Commercial systems offering COBOL 60 compilation supported installations at Internal Revenue Service, Social Security Administration (United States), Bank of America, Wells Fargo, Sears, Roebuck and Co., and Chase Manhattan Bank. Universities such as MIT, Stanford University, Harvard University, and Princeton University used teaching implementations derived from research at RAND Corporation and Naval Ordnance Laboratory. Vendors like Applied Data Research and consultancies affiliated with Arthur Andersen produced tooling, while maintenance and conversion projects involved contractors including Booz Allen Hamilton and IBM Global Services.

Influence and Legacy

COBOL 60 shaped subsequent standards and influenced languages and systems associated with COBOL, PL/I, SQL, RPG, and business processing frameworks used by Federal Reserve System operations, IRS systems, Social Security Administration (United States), and multinational firms like General Electric and AT&T. Its legacy persisted in large-scale legacy modernization efforts led by IBM, Accenture, Deloitte, Capgemini, and CGI Inc. and in academic studies at Harvard University, Stanford University, and MIT. The specification’s role in governance of software procurement affected procurement policies at U.S. Department of Defense, General Services Administration, and national banks including Bank of America and Chase Manhattan Bank, informing digital transition programs in public institutions such as Internal Revenue Service and Social Security Administration (United States).

Category:Programming languages