Q: Is Cobol primarily used in business? ¶
A: Yes, and finance, and administrative systems for companies and governments.
Q: Is Cobol still widely used in legacy applications deployed on mainframe computers? ¶
A: Yes, such as large-scale batch and transaction processing jobs.
Q: Is Cobol declared hierarchically through the use of level-numbers which indicate if a data item is part of another? ¶
Q: Was Cobol outdated or dead and that 55% believed their students thought COBOL was outdated or dead? ¶
Q: Is Cobol an industry language and is not the property of any company or group of companies? ¶
A: Yes, or of any organization or group of organizations.
Q: Was Cobol used for the majority of their internal software? ¶
Q: Is Cobol now purely to maintain existing applications? ¶
Q: Was Cobol intended to be a highly portable? ¶
A: Yes, and "common" language.
Q: Was Cobol designed in 1959 by CODASYL and was partly based on previous programming language design work by Grace Hopper, commonly referred to as "the mother of COBOL"? ¶
A: Yes, It was created as part of a US Department of Defense effort to create a portable programming language for data processing.
Q: Is Cobol long variable names? ¶
A: Yes, and English words for commands and the separation of data descriptions and instructions.
Q: Was Cobol created and were not involved in its design? ¶
A: Yes, it was designed from the ground up as a computer language for business, with an emphasis on inputs and outputs, whose only data types were numbers and strings of text.
Q: Was Cobol also intended to be easy for programmers to learn and use? ¶
A: Yes, while still being readable to non-technical staff such as managers.