Downloads & Free Reading Options - Results

From the bitsavers.org collection, a scanned-in computer-related document. burroughs :: A-Series :: MCP 7.0 :: 86001518-307 COBOL ANSI-85 Programming Reference Manual Volume 1 Basic Implementation Feb2003

Training materials

Training materials

Training materials

Training materials

1 Diskette 8 cm

COBOL Programming Course COBOL Programming Course This project is a set of training materials and labs for a "Getting Started" level course on COBOL. How to use There are two sets of materials available Chapters which contain the lessons, broken up into chapters. Labs which contain the source code used in the chapters. Contributing Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change. All contributions must align with the Open Mainframe Project contribution guidelines , including having a DCO signoff on all commits. Governance This project is openly governed, and currently establishing its processes. Stay tuned :-) Credits Thank you to IBM for the initial contribution and Open Mainframe Project for hosting this project. To restore the repository download the bundle wget https://archive.org/download/github.com-openmainframeproject-cobol-programming-course_-_2020-04-15_07-07-16/openmainframeproject-cobol-programming-course_-_2020-04-15_07-07-16.bundle and run: git clone openmainframeproject-cobol-programming-course_-_2020-04-15_07-07-16.bundle Source: https://github.com/openmainframeproject/cobol-programming-course Uploader: openmainframeproject Upload date: 2020-04-15

Various schools are struggling with the introduction of Object Oriented (OO) programming concepts and GUI (graphical user interfaces) within the traditional COBOL sequence. OO programming has been introduced in some of the curricula with languages such as C++, Smalltalk, and Java. Introducing OO programming into a typical COBOL sequence presents some interesting challenges. There are a number of new concepts to introduce along with various design issues that are relatively new to OO program design, such as file maintenance and data objects. Most C++ programming courses tend to work with objects that are more user interface related, such as traditional GUI objects. This paper describes an example of using OO COBOL and Dialog Systems (GUI builder) in an advanced programming applications course. (Author/AEF)

Various schools are struggling with the introduction of Object Oriented (OO) programming concepts and GUI (graphical user interfaces) within the traditional COBOL sequence. OO programming has been introduced in some of the curricula with languages such as C++, Smalltalk, and Java. Introducing OO programming into a typical COBOL sequence presents some interesting challenges. There are a number of new concepts to introduce along with various design issues that are relatively new to OO program design, such as file maintenance and data objects. Most C++ programming courses tend to work with objects that are more user interface related, such as traditional GUI objects. This paper describes an example of using OO COBOL and Dialog Systems (GUI builder) in an advanced programming applications course. (Author/AEF)

Various schools are struggling with the introduction of Object Oriented (OO) programming concepts and GUI (graphical user interfaces) within the traditional COBOL sequence. OO programming has been introduced in some of the curricula with languages such as C++, Smalltalk, and Java. Introducing OO programming into a typical COBOL sequence presents some interesting challenges. There are a number of new concepts to introduce along with various design issues that are relatively new to OO program design, such as file maintenance and data objects. Most C++ programming courses tend to work with objects that are more user interface related, such as traditional GUI objects. This paper describes an example of using OO COBOL and Dialog Systems (GUI builder) in an advanced programming applications course. (Author/AEF)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This study investigated programming activity in COBOL. Attempts were made to identify problem areas so that improvements can be made in COBOL compilers and in the manner in which COBOL is taught. Identification of problem areas was achieved through examining program changes made by student programmers during the development of four differenct COBOL programs. The data, which was collected from a COBOL course at Purdue University, consisted of all versions of all programs submitted for compilation by each student. (Author)

This study investigated programming activity in COBOL. Attempts were made to identify problem areas so that improvements can be made in COBOL compilers and in the manner in which COBOL is taught. Identification of problem areas was achieved through examining program changes made by student programmers during the development of four differenct COBOL programs. The data, which was collected from a COBOL course at Purdue University, consisted of all versions of all programs submitted for compilation by each student. (Author)

This study investigated programming activity in COBOL. Attempts were made to identify problem areas so that improvements can be made in COBOL compilers and in the manner in which COBOL is taught. Identification of problem areas was achieved through examining program changes made by student programmers during the development of four differenct COBOL programs. The data, which was collected from a COBOL course at Purdue University, consisted of all versions of all programs submitted for compilation by each student. (Author)

This study investigated programming activity in COBOL. Attempts were made to identify problem areas so that improvements can be made in COBOL compilers and in the manner in which COBOL is taught. Identification of problem areas was achieved through examining program changes made by student programmers during the development of four differenct COBOL programs. The data, which was collected from a COBOL course at Purdue University, consisted of all versions of all programs submitted for compilation by each student. (Author)

This study investigated programming activity in COBOL. Attempts were made to identify problem areas so that improvements can be made in COBOL compilers and in the manner in which COBOL is taught. Identification of problem areas was achieved through examining program changes made by student programmers during the development of four differenct COBOL programs. The data, which was collected from a COBOL course at Purdue University, consisted of all versions of all programs submitted for compilation by each student. (Author)

This study investigated programming activity in COBOL. Attempts were made to identify problem areas so that improvements can be made in COBOL compilers and in the manner in which COBOL is taught. Identification of problem areas was achieved through examining program changes made by student programmers during the development of four differenct COBOL programs. The data, which was collected from a COBOL course at Purdue University, consisted of all versions of all programs submitted for compilation by each student. (Author)

Several common higher level program languages are described. FORTRAN, ALGOL, COBOL, PL/1, and LISP 1.5 are summarized and compared. FORTRAN is the most widely used scientific programming language. ALGOL is a more powerful language for scientific programming. COBOL is used for most commercial programming applications. LISP 1.5 is primarily a list-processing language. PL/1 attempts to combine the desirable features of FORTRAN, ALGOL, and COBOL into a single language.

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

COBOL and FORTRAN programming courses - Prentice-Hall

COBOL and FORTRAN programming courses - Prentice-Hall

COBOL and FORTRAN programming courses - Prentice-Hall

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

COBOL-400 programming language - General Electric

COBOL-400 programming language - General Electric

Student Program and Data Disk to accompany Structured COBOL Programming, 8/E Year 2000 Update by Nancy Stern and Robert A. Stern. Published by John Wiley & Sons Inc;  Wiley College Software This is the .dsk image of the entire floppy disk. From the embedded README: ---------------------------------------- This disk contains 1) this README file (readme.txt),  2) all of the practice programs for STRUCTURED COBOL PROGRAMMING, 8th edition, by Nancy Stern and Robert A. Stern as well as two additional programs,one from p.25-26 and one from p.157 (in a folder called "programs"), 3) data files for all the programming assignments, in a folder called "data", and 4) year 2000-compliant versions of all the programs that are in the "programs" folder; these are in a folder called "newy2kprograms". The practice programs are called CHxxpp.cbl where xx is the chapter number.  These are ascii files.  If your compiler uses COBOL source programs with a .cbl file extension, then these programs can be translated as is.  If your compiler uses COBOL source programs with a .cob or other file extension, then rename each program so that it has the appropriate extension. Depending upon your compiler you may also have to change the ASSIGN clauses to specify compiler-specific filenames.  If you are using a PC compiler, ASSIGN clauses for sequential files must include the ORGANIZATION IS LINE SEQUENTIAL clause. The data files are called Cxxyy with a .dat or .mst file extension. xx refers to the chapter and yy to the programming assignment in that chapter.  Thus, C0406.dat is the data file for programming assignment six in Chapter 4. As noted, the program files are in a PROGRAM subdirectory and the data files are in a DATA subdirectory.  The programs in the newy2kprograms folder have names similar to those in the programs folder. If you have any questions about these files, feel free to contact the authors via the internet at [email protected].

From the bitsavers.org collection, a scanned-in computer-related document. univac :: system 80 and series 90 :: UP-9207 IMS Action Programming in COBOL and Basic Assembly Language - User Guide

From the bitsavers.org collection, a scanned-in computer-related document. univac :: system 80 and series 90 :: UP-9207 IMS Action Programming in COBOL and Basic Assembly Language - User Guide

From the bitsavers.org collection, a scanned-in computer-related document. burroughs :: LargeSystems :: A-Series :: MCP 3.8 1989 :: 1169901 A Series COBOL ANSI-74 Test and Debug System TADS Programming Guide 3.7 198707

From the bitsavers.org collection, a scanned-in computer-related document. ansi :: X3 :: X3.023-1974 Programming Language - COBOL

From the bitsavers.org collection, a scanned-in computer-related document. ansi :: X3 :: X3.023-1974 Programming Language - COBOL

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

This report studies the applicability of the Theory of Software Science to COBOL Programs. A COBOL analyzer was written to produce the most important Software Science metrics. The analyzer was used to study several COBOL Databases. The analyzer has been distributed to AIRMICS and to several other organizations including Ohio State University, Jet Propulsion Labs, CINCOM INC., and the University of Trondheim, Norway. Using the analyzer we investigated the software Science Effort Estimator and compared this with estimator based on lines of code and on 'cyclometric complexity.' Our experiments show that the software science effort estimator works reasonably well only if a program is properly modularized and if inter-module factors are included. Published reports on our findings are available on request. We also studied the language level hypothesis of software science in a COBOL environment. While the study shows that the mean language level for COBOL falls between those for FORTRAN and PL/I, the study also shows that language level is heavily dependent on the size of the program and that it fluctuates too much to be considered 'constant' as the Halstead theory postulates. (Author)

xii, 209 p. 29 cm

Includes index