TDMS(ID:3257/tdm001)Time-Shared Data Management SystemTime-Shared Data Management System, System Development Coroporation, Santa Monica Related languages
References: in Proceedings of the 22nd national ACM conference 1967, Washington, D.C. view details in Proceedings of the 22nd national ACM conference 1967, Washington, D.C. view details in Proceedings of the twenty-fourth ACM national conference August 1969 view details SYSTEM DEVELOPMENT CORPORATION/TDMS Background. The Time-Shared Data Management System (TDMS) is a general-purpose system for managing data in a time-sharing environment. It is currently being developed by the Technology Directorate of the System Development Corporation (SDC) as a result of work sponsored in part by the Advanced Research Projects Agency (ARPA) of the Department of Defense. TDMS is being designed and implemented for use on the IBM System 360 Model 50. TDMS is an outgrowth of TSS-Lucid System also developed by SDC for the AN/FSQ-32 computer. Summary of Capabilities. TDMS will permit the user to describe and generate a file as well as retrieve and display data from the file on a cathode-ray tube (CRT) device. It also will provide the capabilities to up-date and maintain the file and to generate hard copy reports. TDMS operates under the SDC-provided ADEPT operating system. ADEPT provides a time-sharing environment that we define as an environment having on-line access and multiple access and rapid response. Specific Features. To achieve rapid response in any large data base it is necessary to be able to provide an access mechanism based on content. Inverted files or indexes and associative memories are two techniques used to do this. TDMS uses a type of inverted file. In TDMS a file is stored in a series of associated tables. One group of tables holds the actual data element values. There is a separate table for each defined data element, and only unique data element values are stored in these tables (i.e., no duplicate values). Another table contains the names of the data elements in the files. A third type of table describes the individual data elements and their logical relationships. It also points to tables that contain pointers arranged in sorted order, which point to the tables containing the actual data element values. This system provides a variety of on-line services oriented to users who are not programmers. There are two capabilities in TDMS that can be used to retrieve data. One of these, QUERY, can produce only relatively simple outputs. A typical example is "PRINT JOB TITLE WHERE POSITION EQUALS PROJECT HEAD." The second, COMPOSE/PRODUCE, can produce rather sophisticated outputs. Within COMPOSE, the user describes any number of report formats to TDMS. Each report format has a name and requires several statements to describe the data that is to be output and the way the output will look when it has been produced as a report. PRODUCE provides the user with the capability of requesting any of the report formats previously generated in COMPOSE to produce actual reports. Through two additional programs TDMS has capabilities for modifying data element values and for maintaining files. The UPDATE program allows the user to add, delete, or change data element values. The MAINTAIN program provides for merging, subsetting, extracting, ordering, and restructuring of files. in Proceedings of the twenty-fourth ACM national conference August 1969 view details in Proceedings of the twenty-fourth ACM national conference August 1969 view details in Proceedings of the twenty-fourth ACM national conference August 1969 view details in Proceedings of the twenty-fourth ACM national conference August 1969 view details in Proceedings of the twenty-fourth ACM national conference August 1969 view details in [ACM] ACM Computing Surveys 2(4) Dec1970 view details in [ACM] Proceedings on the ACM SIGFIDET Workshop on Data Description, Access, and Control, San Diego, California (November 1971) view details [321 programming languages with indication of the computer manufacturers, on whose machinery the appropriate languages are used to know. Register of the 74 computer companies; Sequence of the programming languages after the number of manufacturing firms, on whose plants the language is implemented; Sequence of the manufacturing firms after the number of used programming languages.] in [ACM] Proceedings on the ACM SIGFIDET Workshop on Data Description, Access, and Control, San Diego, California (November 1971) view details The exact number of all the programming languages still in use, and those which are no longer used, is unknown. Zemanek calls the abundance of programming languages and their many dialects a "language Babel". When a new programming language is developed, only its name is known at first and it takes a while before publications about it appear. For some languages, the only relevant literature stays inside the individual companies; some are reported on in papers and magazines; and only a few, such as ALGOL, BASIC, COBOL, FORTRAN, and PL/1, become known to a wider public through various text- and handbooks. The situation surrounding the application of these languages in many computer centers is a similar one. There are differing opinions on the concept "programming languages". What is called a programming language by some may be termed a program, a processor, or a generator by others. Since there are no sharp borderlines in the field of programming languages, works were considered here which deal with machine languages, assemblers, autocoders, syntax and compilers, processors and generators, as well as with general higher programming languages. The bibliography contains some 2,700 titles of books, magazines and essays for around 300 programming languages. However, as shown by the "Overview of Existing Programming Languages", there are more than 300 such languages. The "Overview" lists a total of 676 programming languages, but this is certainly incomplete. One author ' has already announced the "next 700 programming languages"; it is to be hoped the many users may be spared such a great variety for reasons of compatibility. The graphic representations (illustrations 1 & 2) show the development and proportion of the most widely-used programming languages, as measured by the number of publications listed here and by the number of computer manufacturers and software firms who have implemented the language in question. The illustrations show FORTRAN to be in the lead at the present time. PL/1 is advancing rapidly, although PL/1 compilers are not yet seen very often outside of IBM. Some experts believe PL/1 will replace even the widely-used languages such as FORTRAN, COBOL, and ALGOL.4) If this does occur, it will surely take some time - as shown by the chronological diagram (illustration 2) . It would be desirable from the user's point of view to reduce this language confusion down to the most advantageous languages. Those languages still maintained should incorporate the special facets and advantages of the otherwise superfluous languages. Obviously such demands are not in the interests of computer production firms, especially when one considers that a FORTRAN program can be executed on nearly all third-generation computers. The titles in this bibliography are organized alphabetically according to programming language, and within a language chronologically and again alphabetically within a given year. Preceding the first programming language in the alphabet, literature is listed on several languages, as are general papers on programming languages and on the theory of formal languages (AAA). As far as possible, the most of titles are based on autopsy. However, the bibliographical description of sone titles will not satisfy bibliography-documentation demands, since they are based on inaccurate information in various sources. Translation titles whose original titles could not be found through bibliographical research were not included. ' In view of the fact that nany libraries do not have the quoted papers, all magazine essays should have been listed with the volume, the year, issue number and the complete number of pages (e.g. pp. 721-783), so that interlibrary loans could take place with fast reader service. Unfortunately, these data were not always found. It is hoped that this bibliography will help the electronic data processing expert, and those who wish to select the appropriate programming language from the many available, to find a way through the language Babel. We wish to offer special thanks to Mr. Klaus G. Saur and the staff of Verlag Dokumentation for their publishing work. Graz / Austria, May, 1973 in [ACM] Proceedings on the ACM SIGFIDET Workshop on Data Description, Access, and Control, San Diego, California (November 1971) view details |