CODASYL is remembered almost entirely for two activities: its work on the development of the COBOL language and its activities in standardizing database interfaces. It also worked on a wide range of other topics, including end-user form interfaces and operating system control languages, but these projects had little lasting impact. The remainder of this section is concerned with CODASYL's database activities. In 1965 CODASYL formed a List Processing Task Force. This group was chartered to develop COBOL language extensions for processing collections of records; the name arose because Charles Bachman's IDS system managed relationships between records using chains of pointers. In 1967 the group renamed itself the Data Base Task Group, and its first report in January 1968 was entitled COBOL extensions to handle data bases. In October 1969 the DBTG published its first language specifications for the network database model which became generally known as the CODASYL Data Model. This specification in fact defined several separate languages: a data definition language to define the schema of the database, another DDL to create one or more subschemas defining application views of the database; and a data manipulation language defining verbs for embedding in the COBOL programming language to request and update data in the database. Although the work was focused on COBOL, the idea of a host-language independent database was starting to emerge, prompted by IBM's advocacy of PL/I as a COBOL replacement. In 1971, largely in response to the need for programming language independence, the work was reorganized: development of the Data Description Language was continued by the Data Description Language Committee, while the COBOL DML was taken over by the COBOL language committee. With hindsight, this split had unfortunate consequences. The two groups never quite managed to synchronize their specifications, leaving vendors to patch up the differences. The inevitable consequence was a lack of interoperability among implementations. A number of vendors implemented database products conforming to the DBTG specifications: the best-known implementations were Honeywell's— originally General Electric's— Integrated Data Store, HP's IMAGE Cullinet's Integrated Database Management SystemIDMS, ICL's 2900 IDMS, Univac's DMS-1100, and Digital Equipment Corporation's DBMS32. Cullinet, originally known as Cullinane Database Systems, obtained the technology from B.F. Goodrich. Cullinet was eventually sold to Computer Associates, which as of 2007 still sells and supports a version of IDMS. ANSI and ISO adopted the Codasyl database specifications under the name Network Database Language, with work taking place within the same working group as SQL standardization. An ISO standard for NDL was ratified as ISO 8907:1987, but, as it never had any practical effect on implementations, it was formally withdrawn in 1998. Some of the CODASYL committees continue their work today, but CODASYL itself no longer exists. The records of CODASYL were donated to the Charles Babbage Institute. CBI also hold the archival records for American National Standards Institute . Interest in CODASYL gradually faded due to growing interest in relational databases beginning in the early 1980s.
