The Environment Division is
optional in a COBOL source element. The Environment Division specifies a standard method of expressing those aspects of a data processing problem that are dependent upon the physical characteristics of a specific computer. This division allows specification of the configuration of the compiling computer and the object computer. In addition, information relative to input-output control, special hardware characteristics and control techniques may be given.
The Environment Division is
optional in a COBOL source element.
ENVIRONMENT DIVISION. [configuration-section] [input-output-section]
If the program includes an
Environment Division, the Environment Division header is optional only if it is
the first division in the program. The Configuration Section is located in the Environment Division . The Configuration Section specifies aspects of the data processing system that are dependent on the specific system as well as special control techniques and a means of associating a local name with an external resource. This section is divided into paragraphs: the Source-Computer paragraph, which describes the computer configuration on which the source element is compiled; the Object-Computer paragraph, which describes the computer configuration on which the runtime module produced by the compiler is to be run; the Special-Names paragraph, which provides a means for specifying the currency sign, choosing the decimal point, specifying symbolic-characters, relating implementor-names to user-specified mnemonic-names, relating alphabet-names to character sets or collating sequences, and relating class-names to sets of characters; and the Repository paragraph, which provides a means for associating a local name with an external resource and specifying which intrinsic function names become reserved words for this source unit.
The Configuration Section is
optional
.
The CONFIGURATION SECTION
header is optional only if it is the first statement in the program.
The Configuration Section
must not be stated in a program that is contained within another program.
The Configuration Section
must not be stated in a method definition.
The
Source-Computer,
Object-Computer and Repository paragraphs must not be stated in a
factory definition or an object definition.The entries explicitly or
implicitly stated in the Configuration Section of a source unit that contains
other source units apply to each directly or indirectly contained source unit.
The Source-Computer paragraph identifies the computer on which the compilation unit is to be compiled.
All clauses of the
Source-Computer
paragraph apply to the source unit in which they are explicitly or implicitly
specified and to any source unit contained within that source unit.The Object-Computer paragraph provides a means of describing the computer on which the runtime module created by the compiler is to be executed.
It is optional.
The MEMORY SIZE clause and
SEGMENT-LIMIT clause are classed as an obsolete elements in the ANSI'85
standard and are scheduled to be deleted from the next full revision of the
ANSI Standard.
All dialects within this
COBOL implementation support the MEMORY SIZE clause and SEGMENT-LIMIT clause
for documentary purposes only. The FLAGSTD Compiler directive can be used to
detect occurrences of this syntax.
Although they are part of the
standard COBOL definition, the MEMORY SIZE clause and SEGMENT-LIMIT clause are
explicitly excluded from the X/Open COBOL language definitions and should not
be used in a conforming X/Open COBOL source program.
The
Object-Computer
paragraph can consist of only the OBJECT-COMPUTER header.
and source elements
contained within it
The Special-Names paragraph provides a means for specifying the currency sign, choosing the decimal point,
specifying
symbolic-characters,
relating implementor-names to user-specified mnemonic-names, relating alphabet-names to character sets or collating sequences, and relating class-names to sets of characters.
You can select one of
several pre-defined parameter passing conventions. Enhancements to the CALL
statement and the PROCEDURE DIVISION header allow these parameter passing
conventions to be used in inter-program communication.
The clauses in the
Special-Names
paragraph may appear in any order.
At the outer level of a
class definition, the CURRENCY, CURSOR and CRT STATUS clauses must not be
specified.
In the factory or object of
a class definition, the only clauses that can be specified are the CURRENCY,
CURSOR, and CRT STATUS clauses.
If the
Special-Names
paragraph is specified in an interface definition, the ALPHABET, CURRENCY and
DECIMAL-POINT clauses are the only permitted clauses. The data-name-1 phrase of
the CURRENCY clause must not be specified.
Function-name refers to an external switch if its name is one of UPSI-0 through
UPSI-7.
or the SWITCH-n
is used,
the associated mnemonic-name cannot be specified anywhere
except in the SET
statement
. At least one condition-name should be associated with it.
No condition-name is
required.
The lowest valid values for numeric literals in the ALPHABET clause are sensitive to the ALPHASTART Compiler directive.
cannot be specified as
floating-point literals or DBCS literals. The words STANDARD-1 and
ASCII are equivalent.
The reserved word IS is
never required in the Special-Names paragraph.
The literals specified in
the literal-4 phrase:
cannot be specified as
floating-point or DBCS literals. Literal-1, ... literal-5
must not specify a symbolic-character figurative constant.
The same
symbolic-character-1 must appear only once in a SYMBOLIC CHARACTERS clause.
The relationship between
each symbolic-character-1 and the corresponding integer-1 is by position in the
SYMBOLIC CHARACTERS clause. The first symbolic-character-1 is paired with the
first integer-1, the second symbolic- character-1 is paired with the second
integer-1; and so on throughout the SYMBOLIC CHARACTERS clause; the division
into IS or ARE phrases is documentary only.
The lowest valid value for integer-1 is sensitive to the SYMBSTART Compiler directive.
There must be a one-to-one
correspondence between occurrences of symbolic-character-1 and occurrences of
integer-1, both within each IS or ARE phrase and within the entire SYMBOLIC
CHARACTERS clause.
The ordinal position
specified by integer-1 must exist in the native character set. If the IN phrase
is specified, the ordinal position must exist in the character set named by
alphabet-name-2; alphabet-name-2 must be described in an ALPHABET clause.
Integer-2 must be an
unsigned integer in the range 0 to 65535.
Data-name-1 of the CURSOR
IS clause must be declared in the Working-Storage section
.
The CRT STATUS clause
specifies a data item into which a status value is moved after each Format 4
or 5
ACCEPT statement. In
some environments, it can be defined only in the first 64K of Working-Storage.
Data-name-2 must be
described in the Working-Storage section and must be three bytes long.
The CURSOR IS clause
specifies the data item to contain the cursor address as used by the ACCEPT
statement.
or ASCII
phrase is specified, the character code set or collating sequence identified is the American Standard Code for Information Interchange, as defined in American National Standard X3.4-1968.
If the STANDARD-2
phrase is specified, the character code set identified is the International
Reference Version of the ISO 7-bit code, as defined in International Standard
646, 7-bit Coded Character Set for Information Processing Interchange.
If the EBCDIC
phrase is specified, the character code set or collating sequence identified is
EBCDIC.
If the NATIVE phrase is specified, the native character code set or native collating sequence is used. The native collating sequence is either ASCII or EBCDIC, as specified by the NATIVE Compiler directive.)
See the appendix Character Sets and Collating Sequences for details of the ASCII code-set and the ASCII and EBCDIC collating sequences and their correspondence.
, or in the
character code set that is used to represent the data
except when this
figurative constant is specified as a literal in the
Special-Names
paragraph
If more than one character has the highest position in the program collating sequence, the last character specified is associated with the figurative constant HIGH-VALUE.
except when this
figurative constant is specified as a literal in the
Special-Names
paragraph
If more than one character has the lowest position in the program collating sequence, the first character specified is associated with the figurative constant LOW-VALUE.
Floating-point literals
cannot be used in a user-specified collating sequence.
When specified as literals
in the Special-Names paragraph, the figurative
constants HIGH-VALUE and LOW-VALUE are associated with those characters having
the highest and lowest positions, respectively, in the native collating
sequence.
The SYMBOLIC CHARACTERS
clause is used to define user-defined words that can be used like figurative
constants. If the IN phrase is not specified, symbolic-character-1 represents
the character whose ordinal position in the native character set is specified
by integer-1. If the IN phrase is specified, integer-1 specifies the ordinal
position of the character that is represented in the character set named by
alphabet-name-2.
The internal representation
of symbolic-character-1 is the internal representation of the character that is
represented in the native character set.
C and R are allowed,
L is allowed,
E cannot be used,
N cannot be used,
G cannot be used,
lowercase alphabetic
characters a through z,
(except e, f, g, h,
i, j, k, m, n, o, q, t, u, w, y);
If this clause is not present, only the currency sign defined in the COBOL character set is used in the PICTURE clause. See the section Character Set in the chapter Concepts of the COBOL Language.
If the NUMERIC SIGN clause
is specified, the default for signed numeric items is for the sign to be stored
as a trailing separate character.
Wherever a mnemonic-name
is allowed, you can use the function-name.
|
TAB |
Skip to Vertical Tabulation Position (inserts ASCII X"0B" in the output record as appropriate) | WRITE ADVANCING statement |
|
PRINTER |
Printer | DISPLAY statement |
|
FORMFEED |
Skip to new page (inserts ASCII X"0C" in the output record as appropriate) | WRITE ADVANCING statement |
|
COMMAND-LINE |
Command transfer | ACCEPT and DISPLAY statements |
|
ARGUMENT-NUMBER
|
Command-Line argument number | ACCEPT and DISPLAY statements |
|
ARGUMENT-VALUE |
Command-Line argument value | ACCEPT statement |
|
ENVIRONMENT-NAME
|
Environment-variable name | DISPLAY statement |
|
ENVIRONMENT-VALUE
|
Environment-variable value | ACCEPT and DISPLAY statements |
|
SYSERR |
Standard error device | DISPLAY statement |
The following table
reflects the support for function names offered by OS/VS COBOL, VS COBOL II and
SAA in this COBOL system.
Table 6-1: Function Names Support
| OSVS | VSC2 Rel (2) | COBOL/370 or VSC2 Rel (3)/(4) |
SAA L1 | |
|---|---|---|---|---|
| SYSIN | y | y | y | y |
| SYSIPT | U | U | y | |
| SYSOUT | y | y | y | y |
| SYSLIST | y | |||
| SYSLST | U | U | y | |
| SYSPCH | U | U | y | |
| SYSPUNCH | U | y | y | |
| CONSOLE | y | y | y | y |
| C01 | y | y | y | y |
| C02 | y | y | y | |
| C03 | y | y | y | |
| C04 | y | y | y | |
| C05 | y | y | y | |
| C06 | y | y | y | |
| C07 | y | y | y | |
| C08 | y | y | y | |
| C09 | y | y | y | |
| C10 | y | y | y | |
| C11 | y | y | y | |
| C12 | y | y | y | |
| S01 | y | y | y | |
| S02 | y | y | y | |
| S03 | U | y | ||
| S04 | U | y | ||
| S05 | U | y | ||
| CSP | y | y | y | y |
| 1 char rw literal | y | |||
| AFP-5A | y |
| y | Documented and accepted by mainframe compilers and the COBOL system. |
| U | Undocumented but accepted by mainframe compiler. |
The CLASS clause provides a
means for relating a name to the specified set of characters listed in that
clause. Class-name-1 can be referenced only in a class condition. The
characters specified by the values of the literals in this clause define the
exclusive set of characters which constitute class-name-1. The value of each
literal specifies:
If the THROUGH phrase is
specified, the contiguous characters in the native character set beginning with
the character specified by the value of literal-4, and ending with the
character specified by the value of literal-5, are included in the set of
characters identified by class-name-1. Additionally, the contiguous characters
specified by a given THROUGH phrase can specify characters of the native
character set in ascending or descending sequence.
The CALL-CONVENTION clause
allows you to select one of several pre-defined parameter passing conventions
which allow you to CALL subprograms written in languages other than COBOL, and
which use different parameter passing conventions.
The CONSOLE IS CRT clause
causes any ACCEPT or DISPLAY statement whose operand is not a screen-name, and
that has no phrases specific to a particular format, to be treated as Format 5.
If the CONSOLE IS CRT clause is not present, these statements are treated as
the standard ANSI ACCEPT or DISPLAY.
The CURSOR IS clause
specifies the data item to contain the cursor address used by the ACCEPT
statement.
The CRT STATUS clause
specifies a 3-byte data item, into which a status value is moved after each
Format 4 or Format 5 ACCEPT statement.
If the CRT STATUS clause
is specified in the Special-Names paragraph, every Format 4
or 5 ACCEPT statement (as described later in this chapter) places a value into
data-name-2 to indicate the outcome of the ACCEPT operation. Data-name-2
consists of status keys which are set to indicate possible conditions resulting
from the completion of the operation. They are described below.
CRT Status Key 1: The first byte of data-name-1 is CRT Status Key 1 and should be described as PICTURE 9 USAGE DISPLAY. It indicates the condition that caused the termination of the ACCEPT operation. The possible values are:
| "0" | indicates a terminator key or auto-skip out of the final field |
| "1" | indicates a user-defined function key |
| "2" | indicates a COBOL system-defined function key |
| "9" | indicates an error |
A terminator key is a key whose purpose is terminating ACCEPT operations (for example, Enter). A particular configuration option causes the field-tab key, when used in the final field of an ACCEPT, to act as a terminator key. Defining function keys is also a configuration option.
A termination that returns a value of "0" is called a normal termination.
If the ACCEPT statement contains an ON EXCEPTION phrase, any value in CRT Status Key 1, except " 0", will cause the execution of the imperative-statement in that phrase.
CRT Status Key 2: The second byte of data-name-1 is CRT Status Key 2 and contains a code giving further details of the condition that terminated the ACCEPT operation. Its format and possible values depend on the value in CRT Status Key 1, as shown in the following table.
Table 6-2: Valid Combinations of CRT Status Keys 1 and 2
| Key 1 | Key 2 | Meaning | |
|---|---|---|---|
| Format | Value | ||
| 0 | PIC 9 DISPLAY | 0 | The operator pressed a terminator key |
| 0 | PIC 9 DISPLAY | 1 | Auto-skip out of the last field |
| 1 | PIC 99 COMP | 0-127 | The function key number |
| 2 | PIC 99 COMP | 0-26 | The function key number |
| 9 | PIC 99 COMP | 0 | No items fall within the screen |
See your COBOL system documentation on screen handling and user interfaces for an explanation of function key numbers.
CRT Status Key 3: The third byte of data-name-1 is CRT Status Key 3 and should be described as PICTURE 99 COMP-X or as PICTURE 99 COMP (with the NOIBMCOMP directive specified). If CRT Status Key 1 and CRT Status Key 2 are zero, then CRT Status Key 3 contains the raw keyboard code for the key that terminated the ACCEPT operation. Otherwise, the contents of CRT Status Key 3 are undefined.
Where a sequence of keystrokes rather than a single key has been configured to perform a single function, only the code for the first keystroke is returned.
The Repository paragraph allows specification of function prototype names, class names, interface names and property names that may be used within the scope of this environment division. It also allows declaration of intrinsic-function-names that may be used without specifying the word FUNCTION.
The class class-name-1 is created from the parameterized class class-name-2 by replacing each specification of the formal parameter by the corresponding actual parameter. This replacement is done after the processing of COPY and REPLACE statements.
The interface interface-name-2 is created from the parameterized interface interface-name-3 by replacing each specification of the formal parameter by the corresponding actual parameter. This replacement is done after the processing of COPY and REPLACE statements.
The input-output section deals with the information needed to control transmission and handling of data between external media and a runtime element.
INPUT-OUTPUT SECTION. [ file-control-paragraph ] [ i-o-control-paragraph ]
The input-output section
can be specified in a program definition or a function definition. Within a
class definition, the input-output section must be specified only in a factory
definition, an object definition, or a method definition. The input-output
section must not be specified within an interface definition.
The File-Control paragraph names each file and allows specification of other file-related information.
The FILE-CONTROL entry names a file and can specify other file-related information.
Although they are a part of
the standard COBOL definition, the RECORD DELIMITER and RESERVE phrases and
ellipses in the ASSIGN clause are explicitly excluded from the X/Open COBOL
language definitions and should not be used in a conforming X/Open COBOL source
program.
Data-name-1 can be declared
in the Data Division as an alpha-numeric or group data item long enough to hold
the external name of the file. If it is not explicitly declared within the
source element, your COBOL system will declare it implicitly as an alphanumeric
data item long enough to hold the maximum permissible size of file-name. If
data-name-1 occurs in the FROM option, the data item must be explicitly
declared in the Data Division.
The NOT OPTIONAL phrase has
effect only when the file is opened input-output.
External-file-reference,
data-name-1, or literal-1 specifies the external name of the file.
If the EXTERNAL or
DYNAMIC option is used, literal-1 must not be specified.
If the DYNAMIC option is
used, the word specified for the external file-name will be interpreted as
external-file-reference.
or a two-character
numeric data item with USAGE DISPLAY
and must not be defined in the File or
LOCAL-STORAGE
Sections of the Data Division.
Data-name-3 must be defined
as a group item of 6 bytes in the Working-Storage or Linkage Section of the
Data Division.
Data-name-4 must be
defined in the Working-Storage Section as an alphanumeric data item.
Literal-2 must be a
one-character nonnumeric literal.
Data-name-5 can be
qualified. It must be defined in the Data Division as a one-character data item
of category alphanumeric. It cannot be defined in the
File or Report Sections of the Data Division.
Character-string must not
be a reserved word, a user-defined word that is defined elsewhere, or a
literal. KEYBOARD means console
input.
DISPLAY means console
output.
PRINTER specifies the
system's main printer.
PRINTER-1 specifies the
system's second printer. Split-key-name is a
concatenation of one or more data items within a record associated with that
file-name. It can be referenced only in START and READ statements.
and any data-names
referenced by split-key-name-1 and split-key-name-2
must be defined within a record description entry associated with the file-name.
Any of these data items
can be defined as any supported data category. However, the key is still
treated as an alphanumeric item for the input and output statements against the
file named > in the SELECT clause.
and any data-names
referenced by split-key-name-1 and split-key-name-2
cannot describe an item whose size is variable. See the section The OCCURS Clause in this chapter.
If the PASSWORD clause is
specified, it must immediately follow its associated RECORD KEY or ALTERNATE
RECORD KEY clause.
subsequent assignments
within any one ASSIGN clause are documentary only.
The RESERVE clause is
documentary only, unless the COBOL system documentation specific to your
operating system indicates otherwise.
Data-name-3, if
specified, is documentary only.
The PASSWORD clause is
documentary only.
Use of the reserved word
DYNAMIC in an ASSIGN clause indicates that the value of literal-1 or
data-name-1 in that ASSIGN clause is the specified file's name in the external
file-storage environment.
Use of the reserved word
EXTERNAL in an ASSIGN clause indicates that external-file-reference identifies
the specified file to the external environment for possible further mapping to
an external file-storage environment-name. (See your COBOL system documentation
on file handling for details on setting up external-file-name for your
particular operating environment.)
If
external-file-reference contains the character "–", then only
that part of the name following the last "–" is used to
identify the file to the external environment.
The DISK option without
external-file-reference, data-name-1 or literal-1 and without the FROM option,
specifies a disk file whose name will be given in a VALUE OF FILE-ID clause in
the file description for the file. If that file description contains no VALUE
OF FILE-ID clause, the name of the disk file is assumed to be the same as
file-name-1 (known as the internal file-name).
If any of the keywords
DISK, KEYBOARD, DISPLAY, PRINTER or PRINTER-1 are followed by
external-file-reference, data-name-1 or literal-1, that keyword is ignored.
The DISK option with the
FROM option specifies a disk file whose name on the disk is the value of
data-name-1. However, if when an OPEN statement is executed for that file,
data-name-1 contains all spaces, the name of the disk file is assumed to be the
same as file-name-1 (known as the internal-file-name).
The SHARING clause
specifies the sharing mode to be used for the file unless it is overridden by
the SHARING phrase of the OPEN statement. This clause also specifies whether
record locks have an effect. Additional details are specified in
the section Sharing
Mode in the chapter Concepts of a Compilation Group . The LOCK MODE clause is an
optional clause in the file control entry and is used to specify the locking
technique used for the file.
If this clause is
omitted, opening the file causes it to become exclusive, with the exception of
OPEN INPUT.
When LOCK MODE IS
EXCLUSIVE is specified, the run unit acquires a lock on the whole file when it
opens the file.
When LOCK MODE IS
AUTOMATIC or LOCK MODE IS MANUAL is specified, the file that the run unit opens
is shareable. Files opened OUTPUT, and indexed and relative files opened EXTEND
are, however, always exclusive.
The ROLLBACK clause
requests transaction logging for a file under those COBOL systems that support
that feature. See your COBOL system documentation on file handling for details
of how it is implemented in your system.
If the ROLLBACK clause is
specified then WITH LOCK ON MULTIPLE RECORDS will automatically be in effect.
The WITH LOCK ON RECORD
clause specifies single record locking for the file.
The WITH LOCK ON MULTIPLE
RECORDS clause specifies multiple record locking for the file. This clause must
be present if multiple record locking is required.
If LOCK MODE IS AUTOMATIC
WITH LOCK ON RECORD is specified for a file, a record lock is acquired by the
execution of the READ statement and is released upon execution of a subsequent
I/O operation on this file, with the exception of a START statement.
If LOCK MODE IS AUTOMATIC
WITH LOCK ON MULTIPLE RECORD is specified for a file, a record lock is acquired
by the execution of the READ statement and is not released until a CLOSE,
COMMIT, ROLLBACK or UNLOCK statement is executed, or until an individual lock
is released by a DELETE statement.
If LOCK MODE IS MANUAL WITH
LOCK ON RECORD is specified, a lock is acquired by a READ statement only if it
includes the WITH LOCK phrase, and is released upon execution of a subsequent
I/O operation on this file, with the exception of a START statement.
If LOCK MODE IS MANUAL
WITH LOCK ON MULTIPLE RECORDS is specified, a record lock is acquired by the
READ WITH KEPT LOCK statement and is not released until a CLOSE, COMMIT,
ROLLBACK or UNLOCK statement is executed.
When the lock mode is
MANUAL or AUTOMATIC, single record locking is assumed unless the WITH LOCK ON
MULTIPLE RECORDS phrase is included.
If a file is defined as
EXTERNAL and the operating system file-name is assigned by means of a
file-name, for example, by use of either the ASSIGN directive or keyword, using
data-name-1 in the SELECT/ ASSIGN statement, or using Format 2 of the VALUE OF
phrase of an FD, then the following rules should be followed:
No violation of these
rules will be detected at compile time, but, if any runtime element in the run
unit violates these rules, the results at run time will be undefined.
For further details of
the effects of record locking, see your COBOL system documentation on file
handling.
Using the LINE ADVANCING
FILE phrase causes a file suitable for a printer to be produced. This file will
have an initial carriage-return character, and each record is written with
AFTER ADVANCING 1 LINE as the default advancing phrase. See your COBOL system
documentation on file handling for further details of the format.
The PADDING CHARACTER
clause is documentary only.
If the associated file
connector is an external file connector, all PADDING CHARACTER clauses in a run
unit which are associated with that file connector must have the same
specification. If data-name-5 is external, it must reference an external data
item.
The RECORD DELIMITER
clause is documentary only.
When LINE SEQUENTIAL
ORGANIZATION is specified either implicitly or explicitly, the file is treated
as consisting of fixed length records, each containing one line of data. The
records are stored with trailing spaces removed. The definition of a line of
data varies among different operating systems. Some terminate line
"records" with one or both of the Carriage Return and Line Feed
characters, and some pad out as fixed length records. Your COBOL system,
therefore, always produces files which are compatible in this respect with the
editor software in any operating system.
The LOCK MODE IS clause is
documentary only.
If the associated file
connector is an external file connector, all file description entries in the
run unit which are associated with that file connector must specify the same
data description entry for data-name-1 with the same relative location in the
associated record.
or split-key-name-1
and data-name-8
or split-key-name-2,
as well as of relative locations within a record, must be the same as that used when the file was created. The number of alternate keys for the file must also be the same as that used when the file was created. This checking is configurable in some environments. (See the KEYCHECK attribute in the Callable File Handler configuration file, which is documented in the section "Configuring the Callable File Handler" of the "Programmer's Guide to File Handling".)
The SUPPRESS phrase
requests the use of a sparse key for an alternate index. Sparse keys are only
available through the Callable File Handler and are not available on all
systems (see your COBOL system documentation on file handling for details).
When the SORT STATUS
clause is specified, a value is placed into the two-character data item
specified by data-name-2 after the execution of each sort operation. This value
indicates the status at completion of the operation.
The resulting status of
the sort operation is indicated by valid combinations of status keys 1 and 2.
For explanations of status keys 1 and 2 and definitions of status, see the
section I/O Status earlier in this chapter.
The following
combinations of status keys are possible. Status key 1=0 and status key 2=0
indicates successful completion. Status key 1=3 and status key 2=0 indicates a
permanent error. If status key 1=9, status key 2 contains an operating system
error message number.
The FILE STATUS clause
can be used instead of a SORT STATUS clause, but is treated as a synonym for
it, when specified for a SORT or merge file.
The I-O-Control paragraph specifies the points at which rerun is to be established, the memory area which is to be shared by different files, and for files with sequential organization the location of files on a multiple file reel.
The RERUN and MULTIPLE FILE
TAPE clauses of the I-O-Control paragraph are classed as
obsolete elements in the ANSI'85 standard and are scheduled to be deleted from
the next full revision of the ANSI Standard.
All dialects within this
COBOL implementation fully support this syntax. The FLAGSTD Compiler directive
can be used to detect all occurrences of this syntax.
Although they are a part of
the standard COBOL definition, the RERUN and MULTIPLE FILE TAPE clauses are
explicitly excluded from the X/Open COBOL language definitions and should not
be used in a conforming X/Open COBOL source program.
More than one SAME clause can be included in a source element, subject to the following restrictions:
Character-string must not
be a reserved word, a literal or a user-name.
Each clause in the
I-O-Control
paragraph may optionally be followed by a period. The RERUN clause is
documentary only.
The APPLY clause is
documentary only.
The MULTIPLE FILE clause is
documentary only.
Copyright © 2001 Micro Focus International Limited. All rights reserved.
This document and the proprietary marks and names
used herein are protected by international law.