SELECT is optional in the FILE-CONTROL paragraph.

If SELECT is used in the FILE-CONTROL paragraph, it must be the first clause. Other clauses may follow it in any order.

Each file described in the Data Division must be specified only once in the FILE-CONTROL paragraph.

On OpenVMS for every format, the first form of ASSIGN TO (marked "OpenVMS ONLY") is available only on the OpenVMS Alpha and OpenVMS I64 operating systems and only if the default /STANDARD=NOXOPEN qualifier is in effect.

The second form of ASSIGN TO is available on the OpenVMS Alpha and OpenVMS I64 systems if the /STANDARD=XOPEN qualifier is in effect.

Each SELECT clause specifying a Report File must have a file description entry containing a REPORT clause in the Data Division of the same program.

You must specify an OPTIONAL phrase for files opened in INPUT, I-O, or EXTEND mode that need not be present when the program runs.

The rules for the OPEN statement describe the effects of the OPTIONAL phrase.

data-name cannot be DISK or PRINTER.

EXTERNAL and DYNAMIC are allowed for syntax compatibility with other COBOL vendors. They are treated as documentation only.

Format 1 is available only on the OpenVMS operating system and only if the default /STANDARD=NOXOPEN qualifier is in effect.

Format 2 is available on Alpha and I64 if the /STANDARD=XOPEN qualifier is in effect.

On UNIX, format 2 is the default.

If there is no VALUE OF ID clause in the file description entry, or that clause contains no file specification, the file specification in the ASSIGN clause is the file specification.

If there is a file specification in an associated VALUE OF ID clause, the ASSIGN clause contains the default file specification. File specification components in the VALUE OF ID clause override those in the ASSIGN clause.

file-spec may contain a logical name.

The file specification derived from one or both of the ASSIGN and VALUE OF ID clauses might refer to an environment variable.

On UNIX systems, "" is not a valid file specification.

On all platforms, file-spec must conform to the rules of the operating system where the run-time I-O occurs.

For indexed files, file-spec must conform to the rules of the ISAM package being used. Some older versions of ISAM on UNIX may have a 10-character maximum for file-spec length.

The BLOCK CONTAINS clause specifies physical record size.

The compiler ignores smallest-block.

The CHARACTERS phrase specifies physical record size in terms of characters.

The physical record size is the maximum of: (1) blocksize bytes, and (2) the size of the largest logical record; plus any overhead bytes for variable-length records.

If there is no BLOCK CONTAINS clause, physical record size assumes a default value.

The physical record size is the size of the largest record plus any overhead bytes.

The size of physical records (in characters) must be a multiple of four. Otherwise, the I/O system rounds up the physical record size to the next multiple of four.

The CODE-SET clause can be in the file's Data Division file description entry. However, it cannot be in both the SELECT clause and the file description entry for the same file.

The CODE-SET clause applies only to files with sequential organization.

The CODE-SET clause identifies alpha-name as the character set used to represent the file data externally.

alpha-name specifies how to convert character codes in the file to and from native character codes.

Code conversion occurs during execution of an input or output operation. Conversion occurs as if the data were USAGE DISPLAY.

Successful OPEN statement execution establishes the character set for code conversion. The set used is the one specified by alpha-name in the FILE-CONTROL paragraph implied by the OPEN statement.

If there is no CODE-SET clause, no character conversion occurs during input-output operations. The native character set is the default.

X/Open standard and VSI standard syntax cannot both be specified for the same file connector. Hence, if LOCK MODE is specified, the ALLOWING, APPLY LOCK-HOLDING, and REGARDLESS phrases cannot be specified for that file.

The WITH LOCK ON RECORD clause is for documentation purposes only.

The LOCK MODE IS MANUAL clause is not available for sequential or line sequential files.

When you specify LOCK MODE IS AUTOMATIC or LOCK MODE IS MANUAL, an OPEN statement (without the WITH LOCK phrase) opens the file in shareable mode. The LOCK MODE clause can be overridden by the WITH LOCK phrase of the OPEN statement.

When you specify LOCK MODE IS EXCLUSIVE, a successful OPEN statement opens the file in exclusive mode. The OPEN statement cannot override LOCK MODE IS EXCLUSIVE.

If you omit the LOCK MODE clause, opening the file causes it to become exclusive, unless you open it for INPUT, in which case the file becomes shareable.

When you specify LOCK MODE IS AUTOMATIC for a file, a record lock is acquired by the successful execution of the READ statement and released on the successful execution of a subsequent I/O statement.

If you specify LOCK MODE IS MANUAL, a record lock is acquired by the READ WITH LOCK statement.

On UNIX, the ROLLBACK phrase is used by ACMSxp applications to specify a recoverable file. You must compile with the -tps option to specify a recoverable file.

A file that is opened in exclusive mode cannot be opened by any other access stream.

A file that is in shareable mode can be opened by any number of access streams that do not require exclusive use.

A file that does not reside on a mass storage device cannot be opened in shareable mode.

File organization is established when the file is created. It cannot be subsequently changed.

If there is no ORGANIZATION clause, the default is SEQUENTIAL.

On Alpha and Itanium systems, when LINE SEQUENTIAL organization is specified, the file is treated as consisting of variable length records, with each record containing one line of data. A line is a sequence of characters ending with a record terminator ( n or x'0A'). The terminator is not counted in the length of the record.

On Alpha and Itanium systems, a file with LINE SEQUENTIAL organization should only contain printable characters and the record terminator.

On Alpha and Itanium systems, a file with LINE SEQUENTIAL organization may not be opened in I-O mode.

All programs that open an existing file must specify the same organization with which the file was created.

The I-O-CONTROL clauses can appear in any order.

More than one APPLY clause can refer to the same file-name.

The phrases of the APPLY clause can appear in any order. However, each phrase can be used only once for each file-name.

You can specify the LOCK-HOLDING phrase only if you specify the ALLOWING option of the OPEN statement.

The RERUN and MULTIPLE FILE clauses cannot refer to a sort or merge file.

In the SAME AREA clause, SORT and SORT-MERGE are equivalent.

If same-area-file refers to a sort or merge file, you must use the SORT, SORT-MERGE, or RECORD phrase.

Files specified in a MULTIPLE FILE TAPE clause must be sequential.

A file cannot be specified in more than one MULTIPLE FILE TAPE clause.

An APPLY clause remains active for a file-name until the image terminates.

If the file connector referenced by file-name is an external file connector, all file control entries in the run unit that reference this file must have the same APPLY clause.

The DEFERRED-WRITE phrase causes a physical write operation to occur only when the input-output buffer for file-name is full. If there is no DEFERRED-WRITE phrase, a physical write occurs each time an output statement executes for file-name.

The EXTENSION phrase specifies the number of disk blocks to be added each time a file is extended. The I/O system extends a file when it needs more file space to add a record.

If extend-amt equals zero, the I/O system extends the file by its default value.

The FILL-SIZE phrase causes the I/O system to use the fill size specified when an indexed file is created to fill the file's buckets. If there is no FILL-SIZE phrase, the I/O system fills buckets completely. The FILL-SIZE phrase applies only to indexed files.

The LOCK-HOLDING phrase declares the VSI standard manual record-locking attribute for a sequential, relative, or indexed file in a file-sharing environment on disk.

Usage of the APPLY LOCK-HOLDING option requires additional syntax for the OPEN, READ, REWRITE, START, and WRITE verbs. Table 4.2, “Required Manual Record-Locking Phrases (VSI Standard) ” summarizes the additional syntax required for Procedure Division I/O statements accessing a file possessing the manual record-locking attribute.

The MASS-INSERT phrase is for documentation only. It has no effect on program execution.

The PRINT-CONTROL phrase specifies that the file has print file format. Additionally, the PRINT-CONTROL phrase applies only to sequentially organized files.

The WINDOW phrase causes the I/O system to use window-ptrs number of retrieval pointers in mapping the files. window-ptrs must fall in the range of 0 to 127 inclusive or be equal to 255. If window-ptrs is 255, then the I/O system attempts to map the entire file.

The SAME AREA clause is for documentation only.

The SAME RECORD AREA clause causes two or more files named by same-area-file to share the same memory area for the current logical records.

If you specify the SAME RECORD AREA clause, more than one same-area-file (or all of them) can be open at the same time.

The logical records start with the same leftmost character position. Thus, the SAME RECORD AREA clause is equivalent to an implicit redefinition of the shared area.

The SAME SORT (SORT-MERGE) AREA clause is for documentation only.

The RERUN clause is for documentation only. It has no effect on program execution.

The MULTIPLE FILE TAPE clause specifies the location of a file or files on a reel/unit device. The location of the file or files can be specified as a relative location by providing a multiple-file series. The specific file location can be specified by the POSITION phrase.

The MULTIPLE FILE TAPE clause specifies the location of a file or files when more than one file shares the same physical reel of tape. If the files in the multiple-file sequence are listed in consecutive order, the POSITION phrase is not required. If the files in the multiple-file sequence are not listed in consecutive order, the position of the file or files (relative to the beginning of the tape) must be specified in the POSITION phrase.

Only those multiple-files referenced by the program need to be specified in a MULTIPLE FILE TAPE clause.

If a file is specified with a POSITION phrase of a MULTIPLE FILE TAPE clause, subsequent files listed in that MULTIPLE FILE TAPE clause which are not specified with a POSITION phrase are assumed to be in the next higher position.

Only one file listed in a MULTIPLE FILE TAPE clause sequence can be open at any one time.

If, at run-time, the run-time system determines that the files referenced are not located on a reel device, the MULTIPLE FILE TAPE clause is ignored.

The level indicator FD identifies the start of a file description entry. It must precede file-name.

The clauses following file-name can appear in any order.

A period (.) separator character must terminate a file description entry.

On OpenVMS, the file name written to disk (see the ASSIGN clause in Chapter 4, Environment Division) has the file type .DAT added if no other file type is specified in the corresponding file specification.

file-name can refer only to a sequential file.

One or more record description entries must follow the file description entry.

file-name can refer only to a relative file.

If a START statement refers to file-name, the file description must include the RELATIVE KEY phrase within the ACCESS MODE clause.

One or more record description entries must follow the file description entry.

file-name can refer only to an indexed file.

On UNIX, for information on file-names for indexed files, see the ASSIGN clause in Chapter 4, Environment Division.

alt-key cannot have the same leftmost character position as that of rec-key or any other alt-key for the same file.

One or more record description entries must follow the file description entry.

file-name can refer only to a report file.

No record description entries may follow the file description entry for a report file.

Only the CLOSE statement and the OPEN statement with the OUTPUT or EXTEND phrase may reference this file description entry.

A file description entry associates file-name with a file connector.

On OpenVMS, if the file description entry contains the EXTERNAL clause, the RMS special registers RMS-STS, RMS-STV, and RMS-FILENAME are external registers.

If the file description entry contains the GLOBAL clause, the RMS special registers RMS-STS, RMS-STV, and RMS-FILENAME are global registers.

If the file description entry contains the LINAGE clause and the EXTERNAL clause, the LINAGE-COUNTER special register is an external data item.

If the file description entry contains the LINAGE clause and the GLOBAL clause, the special register LINAGE-COUNTER is a global name.

If the file description entry contains the EXTERNAL clause, the segmented key seg-key has the external attribute.

If the file description entry contains the GLOBAL clause, the segmented key seg-key is a global name.

The level indicator SD identifies the start of a sort-merge file description. It must precede file-name.

The clauses following file-name can appear in any order.

A period (.) separator character must terminate a sort-merge file description entry.

One or more record description entries must follow the sort-merge file description entry.

report-name must appear in one and only one REPORT clause.

The clauses following report-name may appear in any order. report-name is the highest permissible qualifier that can be specified for LINE-COUNTER, PAGE-COUNTER, and all data-names in the Report Section.

If the Report Description entry contains the GLOBAL clause, report-name and the special registers LINE-COUNTER and PAGE-COUNTER are global names.

The reserved word PAGE-COUNTER references a special register that the compiler creates for each report in the Report Section.

In the Report Section, a reference to PAGE-COUNTER can appear only in a SOURCE clause. In the Procedure Division, PAGE-COUNTER can be used anywhere an integer data item can appear.

If more than one PAGE-COUNTER exists in a program, PAGE-COUNTER must be qualified by a report-name wherever it is referenced in the Procedure Division.

In the Report Section, an unqualified reference to PAGE-COUNTER is qualified implicitly by the name of the report containing the reference. Whenever the PAGE-COUNTER of a different report is referenced, PAGE-COUNTER must be explicitly qualified by the other report's report-name.

The INITIATE statement causes the Report Writer Control System to set the PAGE-COUNTER of the referenced report to one.

PAGE-COUNTER is automatically incremented by one each time the Report Writer Control System executes a page advance.

Procedure Division statements may alter the contents of PAGE-COUNTER.

The reserved word LINE-COUNTER references a special register that the compiler creates for each report in the Report Section.

In the Report Section, a reference to LINE-COUNTER can appear only in a SOURCE clause. In the Procedure Division, LINE-COUNTER can be used anywhere a data item with an integer value can appear. However, only the Report Writer Control System can change the contents of LINE-COUNTER.

If there is more than one LINE-COUNTER in a program, Procedure Division references to LINE-COUNTER must be qualified by a report-name.

In the Report Section, an unqualified reference to LINE-COUNTER is qualified implicitly by the name of the report containing the reference. Whenever the LINE-COUNTER of a different report is referenced, LINE-COUNTER must be explicitly qualified by the other report's report-name.

The INITIATE statement causes the Report Writer Control System to set the LINE-COUNTER of the referenced report to zero. The Report Writer Control System also automatically resets LINE-COUNTER to zero each time it executes a page advance.

The execution of SUPPRESS statements and the processing of nonprintable report groups do not change the value of LINE-COUNTER.

At the time each print line is presented, the value of LINE-COUNTER represents the line number on which the print line is presented. After the presentation of the report group, the value of LINE-COUNTER is governed by the Report Writer Presentation Rules and Tables.

level-number in Format 1 can be any number from 01 to 49, or 77.

The EXTERNAL clause can appear in a level 01 or 77 data description entry in the Working-Storage Section.

The GLOBAL clause can appear in a level 01 or 77 data description entry in the Working-Storage Section, or in a level 01 data description entry in the File Section.

The EXTERNAL and REDEFINES clauses cannot be in the same data description entry.

data-name must appear in any Format 1 entry that contains the EXTERNAL clause or GLOBAL clause, or in the record descriptions of a file description entry that contains the EXTERNAL or GLOBAL clause.

In these cases, there must be no PICTURE clause.

The words THRU and THROUGH are equivalent.

The SYNCHRONIZED, PICTURE, JUSTIFIED, and BLANK WHEN ZERO clauses can appear only in Data Description entries for elementary items.

Each condition-name requires a separate Format 3 entry. The level 88 entry associates one or more values, or ranges of values, with condition-name.

All condition-name entries for an associated data item (the conditional variable) must immediately follow that item's data description entry.

Any condition-name associated with a global conditional variable is global.

Multiple level 01 data description entries subordinate to an FD or SD entry implicitly redefine the same area.

The report group description entry can appear only in the Report Section.

Except for the group-data-name clause, which when present must immediately follow level-number, the clauses may be in any sequence.

An entry containing a LINE NUMBER clause must not have a subordinate entry that also contains a LINE NUMBER clause.

level-number can be any integer from 02 to 48 inclusive.

A Format 2 entry must contain at least one optional clause.

In a Format 2 entry, group-data-name is optional. It can only qualify a sum counter reference.

level-number can be any integer from 02 to 49 inclusive.

A GROUP INDICATE clause can appear only in a DETAIL report group.

A SUM clause can appear only in a CONTROL FOOTING report group.

An entry containing a COLUMN NUMBER clause but no LINE NUMBER clause must be subordinate to an entry containing a LINE NUMBER clause.

group-data-name is optional but can be specified in any entry. group-data-name can be referenced only if the entry defines a sum counter.

A LINE NUMBER clause must not be the only clause specified. Refer to Syntax Rule 3d.

An entry containing a VALUE clause must also have a COLUMN NUMBER clause.

A printable item is a data item whose size and content are specified by an elementary report entry.

An elementary report entry contains a COLUMN NUMBER clause, a PICTURE clause, and a SOURCE, SUM, or VALUE clause.

Figure 5.7, “Format 3 Clause Combinations” shows all permissible clause combinations for Format 3. You read the table from left to right along the selected row.

Format 1 is the Report Group entry. The report group is defined by the contents of this entry and all of its subordinate entries.

The BLANK WHEN ZERO clause, the JUSTIFIED clause, and the PICTURE clause for Report Writer are the same as those in the Data Description Section.

level-number can be any number from 01 to 49.

If the FOREGROUND-COLOR, BACKGROUND-COLOR, or SIGN clauses are specified in both the group screen description entry and the subordinate description entry for a screen item, then the subordinate screen description entry's clauses will take effect.

screen-name assigns a name to the screen item described in the screen description entry and must conform to the rules for user-defined names. If either the optional screen-name or the key word FILLER is specified, it must be the first word following the level number in each screen description entry.

If both screen-name and FILLER are omitted, the screen item being described is treated as though FILLER had been specified, and cannot be referenced in an ACCEPT or DISPLAY statement.

Each level 01 item must have a screen name.

A screen item can be referenced only in an ACCEPT or DISPLAY statement.

The USING phrase is equivalent to the combination of FROM and TO phrases, each specifying the same identifier.

identifier-3, identifier-4 and identifier-5 must be defined in the File, Working-Storage, or Linkage Section.

identifier-1 and identifier-2 must be described as elementary unsigned numeric integer data items.

literal-1 must be a nonnumeric literal.

For a description of picture-string-1, see the PICTURE Clause section of this chapter.

An input screen item is one whose description contains a TO clause.

An output screen item is one whose description contains a FROM clause.

A literal screen item is one whose description contains a VALUE clause.

An update screen item is one whose description contains a USING clause.

An input-output screen item is one whose description contains both a FROM phrase and a TO phrase that may or may not reference the same identifier. The rules for update screen items also apply to input-output screen items.

The LINE and COLUMN clauses should not be specified within a screen description entry in such a way that fields overlap on the screen or fall beyond the screen boundaries.

Format 1 is used for group screen items.

All clauses within a group screen description entry are inherited by subordinate screen description entries with the exception of the BLANK SCREEN clause.

If the SECURE clause is specified, it applies to each subordinate input screen item.

If the AUTO, FULL, or REQUIRED clauses are specified, they apply to each subordinate input and update screen item.

If the BACKGROUND-COLOR, FOREGROUND-COLOR, or SIGN clauses are specified, they apply to each subordinate input, output, and update screen item.

Format 2 is used to describe a literal screen item.

Format 3 is used to describe input, output, or update screen items.

rel-key must be the data-name of an unsigned integer data item whose description does not contain a PICTURE symbol (P). It can be qualified but cannot be in a record description entry for the same file-name.

The ACCESS MODE clause can be in the file's SELECT clause. However, it cannot be in both the SELECT clause and file description entry for the same file.

If the USING or GIVING phrases of a SORT or MERGE statement contain the name of the file, the ACCESS MODE RANDOM clause cannot be used for the file.

If rel-key is associated with an external file connector, rel-key must reference the same data item in every program in the run unit.

If a START statement references a relative file, the program must specify the RELATIVE KEY phrase for that file.

If there is no ACCESS MODE clause, the access mode is sequential.

For random access, the value of rel-key (for relative files) or a Record Key data item (for indexed files) indicates the record to be accessed.

For dynamic access, the program can access records sequentially and randomly.

Relative record numbers uniquely identify records in relative files. A record's relative record number identifies its ordinal position in the file. The first record in the file has a relative record number of 1. Subsequent records have consecutively higher relative record numbers.

The Relative Key data item associated with the execution of an Input/Output statement is rel-key in the file description entry (or SELECT clause) associated with the statement.

The ALTERNATE RECORD KEY clause can be in the file's SELECT clause. However, for the same file, it cannot be in both the SELECT clause and file description entry.

alt-key or the segments of seg-key cannot have the same leftmost character position as that of the Prime Record Key data item or any other alt-key or segment of seg-key for the same file.

seg-key is the concatenation of all specified key segments in the order specified.

seg-key can be referenced only in a READ (Format 3) or START statement.

The DUPLICATES phrase specifies that two or more records in the file can have duplicate values in the same alt-key or the segments of seg-key. If there is no DUPLICATES phrase, two records cannot have the same value in corresponding Alternate Record Keys.

On OpenVMS, if the program was compiled with the /CHECK=DUPLICATE_KEYS qualifier on the command line, and the duplicate key specification on a file's FD (in other words, specified in the WITH DUPLICATES phrase) does not match that of the actual file, a run-time diagnostic will be issued when an attempt is made to open the file with an OPEN statement.

The /CHECK=DUPLICATE_KEYS qualifier is not supported for remotely accessed files. Duplicate keys, key length, and number of keys are not checked for remote files, that is, files accessed over the network.

On UNIX systems, DUPLICATES must match the specification for DUPLICATES when the file was created, unless the relaxed key check option is used.

If a file has more than one record description entry, only one of these record description entries must describe alt-key or the segments of seg-key. The character positions referenced by alt-key or the segments of seg-key in that record description are implicitly referenced in all other record description entries for the file.

A file can have up to 254 Alternate Record Keys.

If the associated file connector is an external file connector, all File Description entries in the run unit that are associated with the file connector must define the same data description entry for alt-key or the segments of seg-key, with the same relative location within the record.

Each key can be specified as ASCENDING or DESCENDING (ASCENDING is the default). In an ASCENDING key, lower key values occur toward the beginning of the sorted file. In a DESCENDING key, higher key values occur toward the beginning of the sorted file.

If the AUTO clause is specified at group level, it applies to each input and update screen item in that group.

The AUTO clause is significant in the context of an ACCEPT.

The AUTO clause is ignored in the description of an output screen item.

If there is only one field to input, or if the field is the last one of the screen, the ACCEPT statement is completed when the last character of the field is entered.

The BACKGROUND-COLOR clause is effective only with color screens.

If the BACKGROUND-COLOR clause is omitted, the initial default background color is black.

If the clause is specified at group level, it applies to all subordinate screen items.

If the BLANK SCREEN clause is specified and the BACKGROUND-COLOR clause is specified or inherited, then when a DISPLAY statement displays the screen item, the specified color becomes the default background color. It remains the default background color until another screen item with this combination of options is displayed (whether in the same DISPLAY statement or in another).

The BLANK SCREEN clause can be specified for any screen description entry.

The BLANK LINE clause can be specified only for elementary screen description entries.

The BLANK SCREEN clause executes before a screen item displays, no matter where it appears in the screen item's description. When the BLANK SCREEN clause is specified, the screen is cleared and the cursor is placed at line 1, column 1.

When BLANK LINE is specified in an elementary screen item's description, blanking begins at column 1 of the specified line and continues through to the end of the line.

If neither the BLANK clause nor the ERASE clause (Alpha, I64) is specified, only the particular character positions corresponding to the screen item are modified when the item is displayed. The remainder of the screen content is not changed.

The BLANK SCREEN clause returns the screen to the initial defaults for background and foreground color if the BACKGROUND-COLOR and FOREGROUND-COLOR clauses are not specified, respectively.

The BLANK clause is ignored in an ACCEPT statement.

The BLANK WHEN ZERO clause can be used only for a numeric or numeric edited elementary item.

A data item or screen item containing the BLANK WHEN ZERO clause must be implicitly or explicitly described with DISPLAY usage.

The syntax for a data item allows the spelling ZERO or ZEROES or ZEROS. The syntax for a screen item allows the spelling ZERO only.

The BLANK WHEN ZERO clause causes a data item or screen item to contain spaces when its value is zero.

When the data item or screen item has a numeric PICTURE string, the BLANK WHEN ZERO clause makes the item's category numeric edited.

The BLANK WHEN ZERO clause is ignored in the description of an input screen item.

When the CODE clause is specified, report-code is automatically placed in the first two character positions of each Report Writer logical record.

The positions occupied by report-code are not included in the description of the print line, but are included in the logical record size.

The COLUMN NUMBER clause can be specified only at the elementary level within a report group. The COLUMN NUMBER clause, if present, must appear in a Format 3 Report Group Description entry, or be subordinate to an entry that contains a LINE NUMBER clause in a Format 2 Report Group Description entry.

A printable item is a data item whose size and content is specified by an elementary report entry.

An elementary report entry contains a COLUMN NUMBER clause, a PICTURE clause, and a SOURCE, SUM, or VALUE clause.

Each printable item within a given print line must be defined in ascending column number order such that each printable item occupies a unique sequence of contiguous character positions.

The COLUMN clause can be specified only in an elementary screen description entry.

identifier-1 cannot be subscripted.

The absence of a COLUMN NUMBER clause indicates that the entry is not printable.

Column number 1 is the leftmost position of the print line.

column-num specifies the column number of the leftmost character position of the printable item.

The Report Writer Control System supplies space characters for all positions of a print line not occupied by printable items.

The COLUMN clause, in conjunction with the LINE clause, establishes the starting position for a screen item. This position is an offset from the starting screen coordinates specified in the ACCEPT or DISPLAY statement. The COLUMN clause specifies the horizontal coordinate.

The COLUMN clause without the PLUS phrase specifies the absolute column position of the screen item.

The COLUMN clause with the PLUS phrase specifies a column number relative to that at which the preceding item ends, regardless of whether or not the ACCEPT or DISPLAY statement displays the preceding item on the screen.

A setting of COLUMN 1 is assumed in screen description entries that specify the LINE clause but omit the COLUMN clause.

control-name can be qualified.

Each occurrence of control-name must identify a different data item.

control-name must not have a variable-occurrence data item subordinate to it.

If the associated report file connector is an external file connector, control-name must reference the same external data item in all programs in the run unit.

The word FINAL specifies the most major control item. From here, the hierarchy descends to control-name, which is the major control; to the next recurrence of control-name, which is an intermediate control; and so forth to the last recurrence of control-name, which is the minor control.

A control break is a change in the value of a control-name.

FINAL is used when the most inclusive control group in the report is not associated with a control-name.

The first time a GENERATE statement is executed, the Report Writer Control System (RWCS) saves the values of all control data items associated with that report. After that, every time a GENERATE statement is executed, the RWCS tests those control data items to see if their values have changed. If so, a control break occurs. This control break is associated with the highest level control item whose value has changed.

Control breaks cause the RWCS to present appropriate CONTROL HEADER and CONTROL FOOTING report groups for printing. Figure 5.8, “Control Break Levels and Their Printed Report Groups” shows the report groups the RWCS processes (X) when you define FINAL, major, intermediate, or minor control-name in a CONTROL HEADING or CONTROL FOOTING phrase in a Report Group Description entry. For example, if the value in a major control-name changes, the RWCS processes all major, intermediate, and minor control groups specified in CONTROL HEADING and CONTROL FOOTING report groups.

In the following example, a report defines four control totals in the control clause. The source of these control totals is in an input file—INPUT-FILE. The file is presorted in ascending sequence by MAJOR-CONTROL, INTERMEDIATE-CONTROL, and MINOR-CONTROL. The RWCS will monitor these fields in the input file for any changes. If a new record contains data different from the previous record read, the RWCS triggers a control break.

FILE SECTION.

FD      INPUT-FILE...
01      INPUT-RECORD.
    02    MAJOR-CONTROL           PIC...
    02    ...
    02    MINOR-CONTROL           PIC...
    02    ...
    02    INTERMEDIATE-CONTROL    PIC...
    02    ...

FD      REPORT-FILE...
        REPORT IS SUMMARY-REPORT.
REPORT SECTION.
RD      SUMMARY-REPORT...
        CONTROLS ARE FINAL
                     MAJOR-CONTROL
                     INTERMEDIATE-CONTROL
                     MINOR-CONTROL.

01  DETAIL-LINE TYPE IS DETAIL...

01  TYPE IS CONTROL FOOTING FINAL ...
01  TYPE IS CONTROL FOOTING MINOR-CONTROL...
01  TYPE IS CONTROL FOOTING MAJOR-CONTROL...
01  TYPE IS CONTROL FOOTING INTERMEDIATE-CONTROL...

In the File, Working-Storage, and Linkage Sections, data-name or the key word FILLER (if present) must be the first word after the level-number in each data description entry.

In the Report Section, data-name need not appear in a report group description entry and the key word FILLER must not be used.

If there is no data-name or FILLER clause, the compiler treats the data item as a FILLER item.

The key word FILLER can name a data item. However, a program cannot explicitly refer to FILLER items.

The key word FILLER can name a conditional variable. A program cannot refer to the conditional variable. However, it can refer to the value of the conditional variable by referring to its associated condition-names.

If this clause is omitted, the Report Writer Control System does not allow explicit references to the data item.

Elementary FILLER items:

01  ITEMA.
    03  FILLER PIC X(10) VALUE SPACES.
    03  PIC X(2) VALUE "AB".
    03  PIC 9 VALUE 6.

Group FILLER items:

01  FILLER.
    03  ITEMA     PIC X(4).
    03  ITEMB     PIC 9(7).
    03  FILLER.
        05  ITEMC PIC X.
        05  ITEMD PIC 9(8)V99.
    03  ITEME     PIC X.

Report Writer items:

01  DETAIL-LINE TYPE IS DETAIL.
    02  LINE 10.
        03  DL-NAME     COLUMN 1   SOURCE INPUT-NAME.
        03              COLUMN 25  SOURCE INPUT-ADDRESS.