Fact-checked by Grok 2 weeks ago

CODASYL

CODASYL, an acronym for Conference on Data Systems Languages, was a U.S.-based committee established in 1959 by the Department of Defense to develop standardized languages and systems for data processing, most notably creating the COBOL programming language in 1960, which became a cornerstone of business computing.^[1] The organization also pioneered advancements in database technology through its Data Base Task Group (DBTG), formed between 1965 and 1967, which released the first specifications for a network database model in 1969—later refined in the influential 1971 report—to enable more flexible data organization beyond rigid hierarchical structures.^[1]^[2] The CODASYL network model represented data as interconnected records linked via sets, supporting complex relationships such as many-to-many associations without strict parent-child dependencies, and included dedicated languages for data description (DDL) and manipulation (DML) to promote data independence.^[2]^[3] This approach contrasted with contemporary hierarchical models like IBM's IMS by allowing navigational access through directed graphs, though it required programmers to explicitly traverse these "pointers" or sets, often leading to complex query formulations.^[3]^[4] By the early 1970s, the model gained commercial traction, influencing systems like Integrated Data Management System (IDMS) and competing directly with emerging relational models proposed by E. F. Codd in 1970.^[1]^[3] Despite its initial success in the 1970s, when CODASYL specifications were updated in 1973 to better integrate with host languages like COBOL, the model's navigational complexity and lack of declarative querying hindered its long-term adoption compared to the simpler relational paradigm.^[2]^[3] The committee's activities waned by the 1980s as relational databases, exemplified by IBM's DB2 in 1984, dominated the market, but CODASYL's emphasis on graph-like structures foreshadowed later technologies like XML and NoSQL graph databases.^[1]^[3] Today, while the organization no longer exists as a formal entity, its legacy endures in foundational concepts of data modeling and the enduring popularity of COBOL in legacy enterprise systems.^[1]

History

Formation and Early Objectives

The Conference on Data Systems Languages (CODASYL) was formed on May 28–29, 1959, during an inaugural meeting attended by approximately 40 representatives from U.S. government agencies, computer manufacturers, and users, held at the Pentagon.^[5]^[6] Sponsored by the U.S. Department of Defense (DoD), the organization emerged from a DoD initiative to address the inefficiencies caused by the hundreds of diverse computers in use across federal systems, each requiring proprietary, machine-specific programming languages that complicated software sharing and maintenance.^[6] The primary objective of CODASYL was to develop a standardized, common business-oriented programming language that would enable efficient data processing across different hardware platforms, replacing ad-hoc, low-level coding practices prevalent on systems like the UNIVAC and IBM 1401.^[5]^[7] This language aimed to use English-like notation for readability, minimize programming effort, simplify training for non-expert users, and ensure portability to future computers with reduced conversion costs.^[5] Early membership included key U.S. government entities such as the DoD, National Bureau of Standards, U.S. Navy, and U.S. Air Force, alongside major manufacturers like IBM, Remington Rand (UNIVAC), Burroughs, General Electric, Honeywell, NCR, Philco, RCA, Sylvania, and International Computers and Tabulators (ICT).^[5]^[8] At the first meeting, CODASYL established an executive committee to oversee operations and formed three specialized groups: the Short Range Committee for immediate language development, the Intermediate Range Committee for mid-term enhancements, and the Long Range Committee for long-term research.^[5] The Short Range Committee, comprising representatives from the Air Force, Navy, and National Bureau of Standards, focused on integrating features from existing languages like FLOW-MATIC, AIMACO, and Commercial Translator to produce usable specifications quickly.^[5]^[6] This effort culminated in the committee's preliminary specifications for COBOL (Common Business-Oriented Language), released on December 17, 1959, marking a foundational step toward a portable business programming standard.^[9] Over the ensuing decades, CODASYL's mandate broadened to encompass database management standards, though its foundational work centered on programming language unification.^[5]

Key Milestones and Evolution

The release of the first COBOL specification in April 1960 marked a pivotal achievement for CODASYL, providing a standardized business-oriented programming language designed for portability across diverse computer systems.^[9] This document, developed through collaborative efforts among government, industry, and academic representatives, outlined the core syntax and semantics that would underpin subsequent implementations. In 1962, the U.S. Department of Defense formally adopted COBOL as the mandated language for all defense-related business applications, accelerating its widespread implementation by major computer manufacturers and ensuring its role as a cornerstone of early data processing.^[10] To tackle emerging challenges in file management and data organization, CODASYL formed the Data Base Task Group (DBTG) in May 1967, evolving from the earlier List Processing Task Force to focus on extensions for handling complex data structures in COBOL environments.^[11] The DBTG's inaugural report, published in October 1969, introduced foundational specifications for data description and manipulation languages, proposing a network-oriented model to support integrated data storage and retrieval.^[11] This was followed by an updated report in April 1971, which incorporated over 130 refinements based on feedback, enhancing the schema definition and navigational capabilities while maintaining compatibility with COBOL.^[12] The final journal version appeared in 1973 as the CODASYL Data Description Language Journal of Development, solidifying these proposals into a comprehensive standard for database management systems.^[11] CODASYL's international expansion gained momentum in 1971, with the April DBTG report distributed in Europe through partnerships with the British Computer Society and the International Federation for Information Processing (IFIP), fostering global adoption of its data standards.^[11] Throughout the 1970s, CODASYL sustained its influence via annual conferences and the ongoing Journal of Development series, which documented iterative advancements in language specifications and data handling.^[13] These efforts directly shaped national standards, including the American National Standards Institute (ANSI) COBOL revisions, where CODASYL's updates through 1971 informed the 1974 standard's enhancements for structured programming and data base integration.^[14]

Decline and Dissolution

By the mid-1970s, the database industry began shifting toward the relational model, exemplified by the development of SQL in IBM's System R project starting in 1974, which diminished the prominence of CODASYL's network approach due to the latter's complexity in navigation and lack of data independence.^[15] This transition was accelerated by the relational model's emphasis on declarative querying and automatic optimization, contrasting with CODASYL's record-at-a-time programming paradigm.^[15] The Data Base Task Group (DBTG) issued its last major report in 1978, building on the 1973 specifications but incorporating enhancements that failed to stem the tide of declining interest. Thereafter, CODASYL's activities reduced significantly, as key members including the U.S. Department of Defense prioritized ANSI and ISO standardization efforts for broader interoperability over CODASYL's proprietary-style committee work.^[16] Contributing to this decline was vendors' reluctance to fully implement the intricate CODASYL database standards, which demanded substantial development resources for limited market alignment.^[17] Concurrently, IBM's hierarchical IMS system, introduced in the late 1960s, dominated enterprise environments without adopting CODASYL, while relational DBMS like Oracle's SQL product gained traction by the early 1980s.^[15] CODASYL's activities ceased in the late 1980s, with its COBOL-related assets and ongoing development responsibilities transferred to ANSI's X3J4 committee to continue under formal standards bodies.^[16]^[18]

COBOL Development

Initial Specifications

The development of the initial COBOL specifications began in June 1959 when the Conference on Data Systems Languages (CODASYL), formed earlier that year to standardize business programming languages, established a nine-member Short-Range Committee tasked with producing a preliminary language design within six months.^[19] This committee, comprising representatives from computer manufacturers and users, completed its work by December 1959, resulting in the report titled "Specifications for a Common Business Oriented Language."^[20] The document outlined a high-level language aimed at unifying disparate business programming efforts across systems. The specifications structured COBOL programs into four primary divisions: Identification, which provided program metadata such as author and installation details; Environment, which described the computing setup including input-output configurations; Data, which defined variables and records using clauses like PICTURE for specifying formats (e.g., PIC 9(5) for a five-digit numeric field); and Procedure, which contained the executable logic through statements like ADD, MOVE, and PERFORM.^[9] These divisions emphasized a hierarchical, self-documenting format to separate concerns and facilitate maintenance. Guided by principles of being problem-oriented, machine-independent, and readable even by non-technical users, the design drew significant influence from Grace Hopper's FLOW-MATIC language, which pioneered English-like syntax for data processing, and IBM's COMTRAN, which contributed concepts for commercial data manipulation.^[20] This approach prioritized portability across hardware, using verbose keywords to mimic natural language and reduce the need for specialized training. Following review and minor adjustments, the Executive Committee endorsed the specifications on January 8, 1960, with formal Department of Defense (DoD) adoption occurring by February 1960, mandating COBOL support for future procurements.^[9] Initial implementations emerged rapidly, with successful tests demonstrating a single COBOL program running unchanged on a UNIVAC and an RCA computer in December 1960; separate efforts also produced a COBOL processor for the IBM 1401 around the same period.^[21]

Revisions and Standardization Efforts

Following the initial 1960 specifications, the CODASYL COBOL committee released a revised version in 1961 that introduced key features such as the Report Writer for generating formatted output and basic table handling to support repetitive data structures, enhancing the language's utility for business reporting and data organization.^[5] The 1965 version built on this foundation with intermediate structure improvements, including facilities for mass storage file handling and refined table handling mechanisms, which addressed ambiguities in prior implementations and improved portability across hardware.^[5] The 1968 COBOL Journal of Development represented a comprehensive update, standardizing modules for data manipulation—such as enhanced arithmetic operations, indexing, subscripting, and the MOVE and PERFORM statements—and I-O control, including the FILE-CONTROL and I-O-CONTROL paragraphs for better file access modes and rerun capabilities, all aimed at achieving uniform source programs and object results.^[5] This revision, approved as USA Standard COBOL X3.23 by the USASI Committee X3, emphasized hardware independence and consistency in data description.^[5] Subsequent revisions in 1974 and 1985, under ANSI oversight with input from CODASYL journals, incorporated structured programming elements like END phrases (e.g., END-IF, END-PERFORM) and enhanced PERFORM statements with VARYING and UNTIL clauses to promote modular code; nested IF statements with explicit scope terminators for complex conditional logic; and validation features such as the FILE STATUS clause, INVALID KEY phrases, and the VALIDATE facility for data integrity checks during I-O operations.^[22]^[23] Throughout these efforts from 1961 to the 1980s, CODASYL's Programming Language Committee and Maintenance Committee played a central role in maintaining backward compatibility across revisions by reviewing implementations, incorporating user feedback from vendors and the data processing community, and issuing journals to refine the language based on practical experiences, ensuring broader applicability before transitioning primary standardization to ANSI.^[5]^[22]

Database Standards

Data Base Task Group Formation

The Data Base Task Group (DBTG) was formed in May 1967 under the auspices of CODASYL's Programming Language Committee, when the existing List Processing Task Force—originally established in 1965 to explore extensions for handling collections of records in COBOL—voted to rename itself and refocus on broader database management challenges, including multi-access file systems that exceeded the limitations of flat-file structures.^[11] This shift addressed the growing demand in the late 1960s for standardized data handling amid increasing computational complexity in business applications.^[24] The DBTG convened initial meetings throughout 1968, emphasizing the development of schema definitions to describe database structures logically and introducing concepts of data independence, which aimed to insulate application programs from changes in physical data storage and access methods.^[24] These early discussions built on the group's biannual meeting rhythm, fostering collaboration among members to outline foundational principles for integrated data systems.^[24] In October 1969, the DBTG issued its first report to the CODASYL Programming Language Committee, presenting an initial navigational data model that utilized owner-record-set structures to enable pointer-based navigation through interrelated records, marking a pivotal step toward standardized database architectures.^[24] The group's membership comprised technical experts from leading organizations, including Honeywell, IBM, RCA, and Burroughs, alongside representatives from universities such as those contributing to early systems research; this diverse composition was influenced by prior explorations in list processing techniques for dynamic data manipulation.^[25]

Network Model Specifications

The CODASYL network database model, formalized in the 1971 Database Task Group (DBTG) report, structures data around record types and set types to represent complex relationships in a hierarchical yet flexible manner. A record type is a named collection of data items or groups of items, serving as the basic unit for storing entity information, such as a customer record containing fields like name, address, and balance. Set types define owner-member relationships, where one record type acts as the owner (e.g., a department record) and one or more record types serve as members (e.g., employee records linked to the department), enabling many-to-one associations that support modeling of real-world many-to-many scenarios through multiple sets. Linkages between records are maintained via pointers in the form of database keys—unique identifiers assigned by the database management system (DBMS)—which form ring structures for efficient traversal without requiring explicit foreign keys. The model employs three architectural levels: the schema, which describes the entire database's logical structure including all record and set types; the subschema, which provides a tailored view of the database for specific applications or users by selecting subsets of records and sets; and the data subschema, introduced in later refinements to handle physical storage mappings.^[11]^[26]^[27] Access to data in the CODASYL model relies on navigational queries through a Data Manipulation Language (DML) embedded in host programming languages, emphasizing pointer-based traversal rather than declarative queries. Key mechanisms include DML commands such as FIND, GET, STORE, and MODIFY, which operate on records by following set linkages. Navigation is facilitated by currency indicators, which track the most recently accessed positions to maintain context during operations; examples include "current of record" for the last retrieved record instance, "current of set" for the active set occurrence, and "current of run unit" for the overall session. For instance, a FIND NEXT command using "current of set" retrieves the subsequent member record in an owner-member chain, allowing sequential processing of related data like all accounts under a customer. These indicators ensure that applications can "walk" through the network without reloading the entire structure, though this requires programmers to manage paths explicitly. The 1973 DBTG report, via the Data Description Language Journal of Development, refined set ordering and selection clauses to enhance navigation efficiency, such as specifying insertion points or calc keys for indexed access.^[11]^[28]^[26] A core principle of the model is data independence, achieved by decoupling the logical schema—defining record and set structures—from physical storage details managed at the data subschema level, such as file organization or device allocation. This separation allows database administrators to alter storage mechanisms (e.g., from sequential to indexed files) without modifying application code that relies on the subschema. The model further supports flexibility by permitting multiple record types per set, where a single owner can link to diverse member types, as seen in sets with both employee and project records under a department owner, promoting reuse of relationships across the database.^[27]^[11]^[28] Implementation of the CODASYL model integrates seamlessly with COBOL, the primary host language, through extensions in the DATA DIVISION that map database structures to COBOL's data descriptions. Record types are declared using schema-derived clauses like RECORD NAME IS and data items with PICTURE and TYPE specifications, enabling direct I/O via DML verbs embedded in PROCEDURE DIVISION statements—for example, GET CURRENT followed by MOVE operations to transfer data to working storage. This approach, detailed in the 1971 report and expanded in 1973, treats the database as an extension of COBOL's file handling, with subschemas compiled into modules that enforce privacy locks and access controls during program execution.^[26]^[11]

Organization and Influence

Committee Structure

The CODASYL organization was structured around an Executive Committee that provided overall oversight and coordination of activities, ensuring alignment with its objectives for standardizing data systems languages. This committee handled administrative functions, including the adoption of a revised constitution in July 1968 to stabilize operations and reorganize subordinate groups, such as replacing the former Coordinating and Liaison Short Range Committee with a new Planning Committee.^[5] Technical subcommittees operated under the Executive Committee to focus on specific development areas; prominent examples included the COBOL Programming Language Committee (PLC), which evolved from the initial Short Range Committee formed in 1959 and was elevated to full committee status in 1968 to maintain and update COBOL specifications, and the Data Base Task Group (DBTG), established in 1965 to define database management standards.^[5]^[29] These subcommittees typically comprised no more than 25 members, balancing representatives from users and implementers, and reported progress through formal journals and documents approved by the Executive Committee.^[30] Operations centered on collaborative processes, with annual plenary sessions bringing together members for high-level discussions and approvals, supplemented by frequent working group meetings to refine proposals. Decision-making emphasized consensus, achieved through meetings, correspondence, and letter ballots among users and manufacturers, culminating in official reports that documented changes and recommendations.^[31] Separate voting sessions for users and manufacturers ensured balanced input, while publications like the Journal of Development served as key outputs to disseminate consensus-driven advancements.^[5] Funding was secured through voluntary contributions from participating members, including industry users, computer manufacturers, and government agencies such as the Department of Defense, covering costs for manpower, meetings, and administrative support without direct sponsorship from any single entity.^[32] The committee structure evolved over time to address emerging needs, notably with the addition of the End User Facilities Committee (EUFC) in the 1970s as a task group under the Systems Committee, aimed at developing facilities for non-programmer end users to interact with database systems.^[33] This reflected growing recognition of user-centric computing, with the EUFC publishing initial progress reports in 1976 to solicit community feedback. International expansion included efforts to establish liaison mechanisms with global bodies, fostering collaboration through groups like the European Computer Manufacturers Association to align CODASYL standards internationally.^[31] Key roles were filled by chairpersons with expertise in data systems; for instance, the initial CODASYL effort was chaired by Charles A. Phillips, Director of the Data Systems Division at the Department of Defense, who guided the formation of the steering committee in 1959.^[34] Subsequent chairs, often from government or industry, maintained this balance to ensure broad representation in oversight and technical work.

Impact on Industry and Legacy

CODASYL's standards profoundly shaped the computing industry during the mid-20th century, particularly through the widespread adoption of COBOL for business applications. By 1970, COBOL had become the most widely used programming language globally, serving as the backbone for commercial data processing in sectors like finance, government, and manufacturing.^[35] Its English-like syntax and focus on business logic enabled portability across hardware, facilitating the standardization of enterprise software and reducing vendor lock-in. This ubiquity extended to handling a significant portion of global business data. In the database realm, CODASYL's network model, formalized by the Data Base Task Group in 1971, influenced the development of several commercial systems that gained traction in the 1970s and 1980s. Notable examples include IDMS (Integrated Database Management System) from Computer Associates and TOTAL from Cincom Systems, both of which implemented CODASYL specifications to support complex, many-to-many relationships in navigational databases.^[36] These systems were among the leading database packages listed in industry buyer's guides by 1974, powering applications in industries requiring efficient handling of interconnected data, such as inventory management and telecommunications.^[37] However, their adoption highlighted CODASYL's emphasis on structured data navigation, which became a foundation for early enterprise data management. CODASYL's conceptual contributions extended to later technologies, including key ideas in relational databases. The organization's standards proposed a three-level schema architecture (subschema, schema, and data storage description) to promote logical and physical data independence, allowing changes to the database structure without necessarily affecting applications—a concept that influenced the ANSI/SPARC three-schema approach and was further developed in E.F. Codd's relational model of 1970.^[3] Despite these advances, the inherent complexity of CODASYL's navigational approach—requiring programmers to explicitly traverse data links—contributed to its decline by the 1980s, as simpler relational models from IBM and Oracle gained preference for their ease of use and query flexibility.^[15] CODASYL's legacy endures in the persistence of COBOL within legacy systems, where it continues to underpin critical infrastructure in banking and government, handling 95% of ATM transactions and 80% of in-person credit card transactions as of 2023 despite modernization efforts.^[38] In database history, CODASYL is acknowledged as a pivotal step toward standardized data management, with its network model informing discussions on graph and NoSQL databases today, though direct implementations have largely faded. Overall, CODASYL demonstrated the value of consortium-driven standards in fostering industry-wide interoperability, even as evolving needs shifted toward more intuitive paradigms.

References

[1]
CODASYL - Oxford Reference
During 1965–67 CODASYL established a Database Task Group (DBTG) to investigate and develop proposals for a common database management system to be used in ...
[2]
CODASYL Data-Base Management Systems - ACM Digital Library
An in-depth examination of logical data models utilized in data storage systems to facilitate data modeling.
[3]
[PDF] What Goes Around Comes Around
In the mid 1970's Peter Chen proposed the entity-relationship (E-R) data model as an alternative to the relational, CODASYL and hierarchical data models [CHEN76] ...
[4]
Thirty years (and more) of databases - ScienceDirect
At the time it appeared that the relational model was a revolutionary step whereas the CODASYL report was an evolutionary step. ... Database description with SDM: ...Introduction · The Origins Of Data Storage... · The Network Model<|control11|><|separator|>
[5]
[PDF] CODASYL COBOL journal of development 1968
The original COBOL organization was the Short Range Committee of CODASYL. By September, 1959, this committee had specified a language which they considered ...Missing: Defense | Show results with:Defense
[6]
How COBOL Became the Early Backbone of Federal Computing
Sep 21, 2017 · The steering committee met on June 4, 1959, and agreed to name the entire activity as the Committee on Data Systems Languages, or CODASYL, and ...
[7]
A Compelling Image: The Tower of Babel and the Proliferation of ...
... Short Range Committee on 27 and 28 August 1959. Sammet's notes of this meeting contain the agreed table of contents of the report, including the title of ...
[8]
COBOL Session - ACM Digital Library
Jan 2, 2020 · The first meeting of the Short-Range Committee was held at the National Bureau of ... CODASYL Executive Committee (Short-Range Committee, 1959b).
[9]
[PDF] COBOL programming language - Bitsavers.org
The Conference on Data Systems Languages is a voluntary cooperative effort of users of data processing systems (both in the government and industry) and.
[10]
A Short History of Early Cobol - ACM Digital Library
In December 1959, the specifications for Cobol were given to the CODASYL ... This was followed by Cobol-. 61 Extended (issued in 1962), and Cobol-65. The ...
[11]
[PDF] NBS HANDBOOK 113 CODASYL Data Description Language
Three CODASYL committees were agreed upon at the May, 1959, meeting, and an executive committee was established to coordinate the work of the three. The ...
[12]
Data base task group report to the CODASYL programming ...
This report reflects many of the changes, improvements and extensions suggested as a result of publication of the first report. It also reflects ...
[13]
Collection: Conference on Data Systems Languages records
The organization was formed in 1959 to guide the development of a standard programming language that could be used on many computers. This effort led to the ...
[14]
[PDF] LA_ ~b~bU ~ a2ja1977 - DTIC
The 1974 COBOL Standard was derived solely from the CODASYL. COBOL JOD updated through 1971. Please note that the ground rules stated above indicated that ...Missing: influence | Show results with:influence<|control11|><|separator|>
[15]
6 The Rise of Relational Databases | Funding a Revolution
Both the IBM and the Codasyl products were sometimes called navigational databases because they required the user to program or navigate around a data set.
[16]
[PDF] programming language COBOL - NIST Technical Series Publications
Dec 7, 1978 · The language specifications contained in this standard were drawn from both American. National Standard X3.23-1968 and the CODASYL COBOL Journal ...
[17]
[PDF] An Examination of the 1978 CODASYL DDLC Report. - DTIC
Oct 1, 1978 · ommittee's. 1978 Report incorporates numerous enhancements and language changes made since the earlier 1971 and 1973 reports. Unfortunately, the.Missing: DBTG | Show results with:DBTG
[18]
1959: The creation of Cobol - June 8, 1999 - CNN
Jun 9, 1999 · The DOD broke Codasyl into several committees, and by June, the nine-member "short-range committee" was asked to undertake a six-month ...Missing: formation 28-29
[19]
The early history of COBOL - ACM Digital Library
(Report on CODASYL Steering Committee meeting held June 4, 1959.) Google ... {Letter to Charles Phillips transmitting final report of Short-Range Committee ...
[20]
Grace Hopper and Colleagues Introduce COBOL
On May 28 and 29, 1959 a group representing computer users, programmers, manufacturers, universities, and the government met at The Pentagon Offsite Link, ...Missing: CODASYL Short Range preliminary date
[21]
[PDF] programming language COBOL - GovInfo
This standard is a revision of American National Standard for Programming Language. COBOL. ANSI X3.23-1974. The language specifications contained in this ...
[22]
[PDF] programming language COBOL - NIST Technical Series Publications
Technical Committee X3J4 on COBOL was responsible for the preparation of a revision of ANSI X3.23-1974. In performing this task. Technical Committee X3J4 ...
[23]
[PDF] Nineteen Sixties History of Data Base Management.
The CODASYL DBTG was a very hard working group between 1967 and 1971 holding meetings every two months. The first report to the parent committee (the. CODASL ...
[24]
Oral-History:Charles Bachman
Jan 27, 2021 · The first CODASYL DBTG project launched IDS2 and IDMS, the version of IDS implemented, by B. F. Goodrich, for the IBM 360 mainframe. They and ...
[25]
[PDF] CODASYL Data-Base Management Systems ROBERT W. TAYLOR
This article presents in tutorial fashion the concepts, notation, and data-base lan- guages that are defined by the "DBTG. Report." We choose the term DBTG to.Missing: 1967 | Show results with:1967
[26]
[PDF] Network Model - Database System Concepts
The first database-standard specification, called the CODASYL DBTG 1971 report, was written in the late 1960s by the Database Task Group. Since then, a number.
[27]
[PDF] APPENDIX
The DBTG of CODASYL was set up to propose DBMS standards. The DBTG 1971 report. (DBTG 1971) contains schema and subschema DDLs and a DML for use with COBOL. A.
[28]
[PDF] Computer Oral History Collection, 1969-1973, 1977
In July. 1968, after discarding names like the “Short-Range Committee of CODASYL,”. “COBOL Maintenance Committee,” and the “COBOL Language Subcommittee,” the.
[29]
[PDF] VJC A0o31A- AN0 - NASA Technical Reports Server
Feb 10, 1978 · not be members of CODASYL. Typically, the task group would be compose of no more than 25 members, with adequate user and implementer represei.
[30]
Structures of standards-processing organizations in the computer area
The establishment of machinery for effective liaison with CODASYL and any other committees working in the same area with a view to ensuring that European.
[31]
[PDF] COMPUTERS IN COMMAND AND CONTROL - DTIC
from time to time, CODASYL is NOT sponsored by. DOD. All costs (manpower, offices, meeting places, mailing, etc.) are met by voluntary donations from the ...
[32]
A progress report on the activities of the CODASYL End User Facility ...
This technical report is authored and presented by the End User Facility Task Group of the CODASYL Systems Committee to interested members of the computing ...
[33]
Charles A. Phillips - Computer Pioneers
Charles A. Phillips, born 1906, Hastings, Neb.; died March 8, 1985, Washington, DC; chairman of the CODASYL committee and leader in the creation of Cobol.Missing: chairpersons | Show results with:chairpersons
[34]
What is COBOL? COBOL programming explained - InfoWorld
Apr 29, 2020 · ... 1970 COBOL was the most widely used programming language in the world. By 1997, COBOL was believed to be running some 80 percent of business ...The 60-Year-Old Programming... · Cobol History · Cobol Language
[35]
[PDF] The Commercialization of Database Management Systems, 1969 ...
The 1974 Datapro Buyer's Guide con- tained data on six packages: Total, System. 2000, IMS, Adabas, IDMS, and DL/1. Datapro selected these packages because they ...
[36]
History of The CA IDMS Database Management System
Oct 1, 2009 · The origins of IDMS can be traced from Charles Bachman's work on IDS at GE in the 1960s, through its formative years at BF Goodrich in the 1970s.
[37]
[PDF] What Goes Around Comes Around
Moreover, relational views [STON75] offer vastly enhanced logical data independence, relative to. CODASYL. d) Set-at-a-time languages offer substantial ...
[38]
50 Years of Queries - Communications of the ACM
Jul 26, 2024 · The initial work of the H2 committee was focused on developing a network data language (NDL) based on the CODASYL DBTG Report of April 1971. But ...
[39]
What Is COBOL? - IBM
Common business-oriented language (COBOL) is a high-level, English-like, compiled programming language developed specifically for business data processing ...Missing: UNIVAC 1401
[40]
[PDF] An implementation of a CODASYL based data management system ...
Jun 19, 1976 · An implementation of a CODASYL based data management system under the UNIX operating system. Howard, John Edward. Monterey, California: Naval ...