Chapter 4: Introduction to Compilation Group Definition

4.1 Introduction

Part 2 of this book describes the base COBOL language definition.

This chapter describes the structure of the entire compilation group.

The other chapters in this part present material on the four COBOL divisions. Within these divisions, material is presented according to COBOL sections, shown by the headers. Clauses, intrinsic functions and COBOL verbs, are listed in alphabetical order, for ease of use.

Additional language features such as DBCS and Report Writer are supported, and are described in your Language Reference - Additional Topics.

4.2 Compilation Groups

A compilation group is the entire source file that is submitted to the compiler. A compilation group may contain zero, one, or more source units. A compilation group consists of a series of source units. A source unit may contain other source units and these contained source units may reference some of the resources of the source units within which they are contained.

A source unit begins with an Identification Division and includes any
contained source units.

With the exception of
compiler directives,
source text manipulation statements, and
end markers,
the statements, entries, paragraphs, and sections of a source unit are grouped into four divisions that are sequenced in the following order:

Identification Division
Environment Division
Data Division
Procedure Division

The beginning of a division in a source unit is indicated by the appropriate division header. The beginning of the Identification Division may also be indicated by one of the paragraph headers permitted in the Identification Division.

The end of a division in a source unit is indicated by one of the following:

The beginning of a succeeding division in that source unit
The end marker for that source unit
That physical position after which no more source lines occur.

The end of a source unit is indicated by an end marker, if specified, or by the absence of additional source lines in the compilation group.

When a source unit, B, is contained in another source unit, A, it may be directly or indirectly contained. Source unit B is directly contained in source unit A if there is no source unit contained in A that also contains B. Source unit B is indirectly contained in source unit A if there exists a source unit contained in A that also contains B.

A source unit that is directly or indirectly contained within another source unit is considered in these specifications as a separate source unit that may additionally reference certain resources defined in the containing source unit.

The object code resulting from compiling a source unit contained within another source unit is considered in these specifications to be inseparable from the object code resulting from compiling the containing source unit.

A compilation unit is a source unit that is not contained within another source unit. It may be preceded or followed by other compilation units in a compilation group.

A source element is a source unit excluding any nested source units.

A runtime element is the result of compiling a source element.

A runtime module is the result of compiling a compilation unit.

General Format

Syntax Rules

Within a compilation group,
call-prototypes and

function-prototypes

must precede all other types of source units.
If a compilation group contains both a function definition and a function prototype definition with the same externalized name, the signatures of these two compilation units must be the same.
The Data Division of a method in an interface definition can contain only a Linkage Section.
The Procedure Division of a method in an interface definition must contain only a Procedure Division header.
In a call prototype, the PROCEDURE DIVISION header must conform to the rules for a format 2 PROCEDURE DIVISION header and any ENTRY statements must conform to the rules for a format 2 ENTRY statement.

General Rules

In a call prototype, all sections of the Data Division are ignored except for the Linkage Section, and the Procedure Division is ignored except for the PROCEDURE DIVISION header and ENTRY statements.
In a function prototype, all sections of the Data Division are ignored except for the Linkage Section, and the Procedure Division is ignored except for thePROCEDURE DIVISION header.

4.3 End Markers

End markers indicate the end of a definition

General Format

Syntax Rules

An end marker must be present in every source unit that contains, is contained in, or precedes another source unit.
Program-name-1 must be identical to the program-name declared in a preceding Program-ID paragraph.
If a Program-ID paragraph declaring a specific program-name is stated between the Program-ID paragraph and the END PROGRAM marker for program-name-1, then an END PROGRAM marker referencing program-name must precede the END PROGRAM marker referencing program-name-1.
Function-prototype-name-1 must be identical to the function-prototype-name declared in the corresponding Function-ID paragraph.
User-function-name-1 must be identical to the user-function-name declared in the corresponding Function-ID paragraph.
Class-name-1 must be identical to the class-name declared in the corresponding Class-ID paragraph.
Method-name-1 must be identical to the method-name declared in the corresponding Method-ID paragraph.
If the PROPERTY phrase is specified in the Method-ID paragraph, method-name-1 must be omitted.
Interface-name-1 must be identical to the interface-name declared in the corresponding Interface-ID paragraph.
If the source unit terminated by the end marker is contained within another source unit, the next statement must be either the first statement of a source unit or another end marker that terminates the containing source unit.
If the source unit terminated by an end marker is not contained within another source unit, the next statement must be the first statement of a compilation unit.

General Rules

An end marker indicates the end of the specified source unit.