ISO/IEC JTC 1/SC 22/WG 4 - COBOL

This document specifies the syntax and semantics of COBOL. Its purpose is to promote a high degree of machine independence to permit the use of COBOL on a variety of data processing systems. This document specifies: The form of a compilation group written in COBOL. The effect of compiling a compilation group. The effect of executing run units. The elements of the language for which a conforming implementation is required to supply a definition. The elements of the language for which meaning is explicitly undefined. The elements of the language that are dependent on the capabilities of the processor. This document does not specify: The means whereby a compilation group written in COBOL is compiled into code executable by a processor. The time at which method, function, or program runtime modules are linked or bound to an activating statement, except that runtime binding occurs of necessity when the identification of the appropriate program or method is not known at compile time. The time at which parameterized classes and interfaces are expanded. The mechanism by which locales are defined and made available on a processor. The form or content of error, flagging, or warning messages. The form and content of listings produced during compilation, if any. The form of documentation produced by an implementor of products conforming to this document. The sharing of objects and resources other than files among run units.

ISO/IEC TR 24716:2007 specifies the syntax and semantics for XML support in COBOL. The purpose of ISO/IEC TR 24716:2007 is to promote a high degree of portability in implementations, even though some elements are subject to trial before completion of a final design suitable for standardization. This specification builds on the syntax and semantics defined in ISO/IEC 1989:2002.

ISO/IEC TR 24718:2005 gives a complete description of the motivations behind the Ada Ravenscar Profile, to show how conformant programs can be analysed and to give examples of usage. The profile is a subset of the Ada tasking model, restricted to meet the real-time community requirements for determinism, schedulability analysis and memory-boundedness, as well as being suitable for mapping to a small and efficient run-time system that supports task synchronization and communication, and which could be certifiable to the highest integrity levels. The profile has been designed such that the restricted form of tasking that it defines can be used even for software that needs to be verified to the very highest integrity levels.

ISO/IEC 1989:2014 specifies the syntax and semantics of COBOL. Its purpose is to promote a high degree of machine independence to permit the use of COBOL on a variety of data processing systems. ISO/IEC 1989:2014 specifies: the form of a compilation group written in COBOL; the effect of compiling a compilation group; the effect of executing run units; the elements of the language for which a conforming implementation is required to supply a definition; the elements of the language for which meaning is explicitly undefined; the elements of the language that are dependent on the capabilities of the processor. ISO/IEC 1989:2014 does not specify: the means whereby a compilation group written in COBOL is compiled into code executable by a processor; the time at which method, function, or program runtime modules are linked or bound to an activating statement, except that runtime binding occurs of necessity when the identification of the appropriate program or method is not known at compile time; the time at which parameterized classes and interfaces are expanded; the mechanism by which locales are defined and made available on a processor; the form or content of error, flagging, or warning messages; the form and content of listings produced during compilation, if any; the form of documentation produced by an implementor of products conforming to this International Standard; the sharing of resources other than files among run units.

ISO/IEC TR 19755:2003 specifies a feature for finalizing objects in COBOL. The specification is a Type 2 Technical Report so that implementations can be undertaken on an experimental basis. The experience gained is expected to result in an improved specification that can progress to standardization. The purpose of object finalization is to free resources that will not otherwise be freed by the normal garbage collection process. Examples include files that are open, temporary work files, database connections, TCP/IP socket interfaces and network connections.

Adopted as amendment 2 to ISO 1989:1985: ANSI X3.23b-1993, supplement to ANSI X3.23-1985.

Adopts the following national standard: ANSI X3.23a-1989, supplement to ANSI X3.23-1985.

ANSI standard is adopted as International Standard 1989-1985 for the COBOL programming language. This second edition cancels and replaces the first edition (ISO 1989-1978).