NetCOBOL V11.0 Messages

The compile options used to compile the method definition must be the same as those used for the method prototype definition. The compile options specified are ignored.

The subparameter keyword specified in compile option '@1@' is not supported in this operating system. Compile option '@1@' ignored.

Compile option '@1@' can only be specified in a class definition. Compile option '@1@' is ignored.

Compiler option '@1@' cannot be specified with '@2@'. Compiler option '@1@' is ignored.

Compiler option '@1@' cannot be specified for the @2@ compiler directive statement. Compiler option '@1@' is ignored.

Compiler option '@1@' is invalid for this compiler. Compiler option '@1@' is ignored.

Compiler option '@1@' is obsolete. Compiler option '@2@' is assumed.

The compiler option cannot be determined from the '@1@' specified. Compiler option '@1@' is ignored.

Compiler option '@1@' is not supported. Compiler option '@1@' is ignored.

Compiler option '@1@' is obsolete, and is not used in the current system. Compiler option '@2@' is assumed.

Compiler option '@1@' is obsolete and will be invalid in the next version.

An I/O error occurred during access of source program file. The compilation was terminated.

An I/O error occurred during access of object file. The compilation was terminated.

An I/O error occurred during access of debugging information file. Compilation terminated.

An I/O error occurred during access of source analysis information file. The compilation was terminated.

An I/O error occurred during access of repository file. The compilation was terminated.

A fatal compiler error has occurred. (substep-name=@1@, module-name=@2@, detail-code=@3@, line-number=@4@)

The compilation process cannot be continued. If other diagnostic messages have been generated, correct those errors and try the compilation again. (substep-name=@1@, module-name=@2@, detail-code=@3@, line-number=@4@)

There is insufficient memory due to the processing of a type library. (substep-name=@1@)

This source file has an invalid character. The compilation is terminated. (substep-name=@1@, line-number=@2@.)

The character set of the source program file or library text file is not the same as the system. The compilation is terminated.

Compile option '@1@' cannot be specified with '@2@'. Compile option '@1@' is ignored.

Since compile option '@1@' is specified, '@2@' is assumed.

By specifying the compile option @1@, compile option @2@ gets enabled.

Compile option '@1@' cannot be specified in the system locale set being used. Compile option '@1@' is ignored.

There was a failure in the initialization of the character code conversion processing. Please verify that the NetCOBOL Development-Execution environment is correctly installed.

A character that is excluded from the COBOL character set is used. That character is ignored.

A period, comma, or semicolon was not followed by a space. A space is assumed to follow the period, comma, or semicolon.

COBOL words are limited to 30 characters each. The first 30 characters are used as the COBOL word.

The reserved word '@1@' must start in Area A. The reserved word is assumed to start in Area A.

Reserved word '@1@' must start in Area B. The reserved word is assumed to start in Area B.

Character string '@1@' must start in Area B. The character string is assumed to start in Area B.

A national user-defined word exceeded the 30 character limit. Only the first 30 characters of the national user-defined word are used.

A character not in the national character set is used in a national user-defined word. '@1@' is the assumed national user-defined word.

The first character of a national user-defined word is not in the national character set. The national user-defined word is ignored.

A hyphen or minus symbol must not be the first or last character of a national user-defined word. National user-defined word '@1@' is ignored.

A national user-defined word must contain at least one kanji, hiragana, katakana or long tone symbol character. The national user-defined word '@1@' is ignored.

The exponent (following E) of the floating-point literal is invalid. The mantissa (preceding E) is assumed to be a numeric literal.

The mantissa of the floating-point literal has exceeded the 16 digit limit. The first 16 digits are used as the mantissa.

The exponent of the floating-point literal has exceeded the two digit limit. The first two digits are used as the exponent.

The absolute value of the floating-point literal is less than minimum value (exponent underflow). The value of the floating-point literal is assumed to be zero.

The absolute value of the floating-point literal is greater than the maximum value (exponent overflow). The absolute value of the floating-point literal is assumed to be 7.2E75.

The numeric literal has exceeded the @1@ digit limit. The first @1@ digits are used as the numeric literal.

The PICTURE character string has exceeded the 30 character limit. The first 30 characters are used as the PICTURE character string.

The PICTURE character string has exceeded the 50 character limit. The first 50 characters are used as the PICTURE character string.

The indicator area must contain '-', '*', '/', 'D', or blank. A blank is assumed to be specified.

The literal must start in Area B. The literal is assumed to start in Area B.

The continuation line of the literal must have a hyphen in the indicator area and must start with a quotation mark. The continuation of the literal is assumed.

The ending quotation mark of the literal is missing. The characters at the end of Area B are assumed to be a literal.

The literal has exceeded the maximum length. The first x characters is assumed to be the literal.

Nonnumeric literals and hexadecimal nonnumeric literals must be greater than zero in length. A space is assumed.

Boolean literals must be greater than zero in length. It is assumed to be a literal containing the single digit '0'.

National literals must be greater than zero in length. It is assumed to be a space.

A Boolean literal must consist of the Boolean characters 0 or 1. Characters other than 0 or 1 are assumed to be zeros.

Hexadecimal nonnumeric literals must be an even number of characters. A zero is added at the end to make an even number of characters.

@1@ must consist of hexadecimal characters (0 through 9 and A through F). Characters other than hexadecimal characters are assumed to be zero.

The length of the national hexadecimal literal must be a multiple of @1@. The literal is truncated to render it a multiple of @1@.

A separator must follow the character string. A separator after the character string is assumed.

A character string that is continued on multiple lines is limited to 324 characters. The character string is assumed to be comprised of the first 324 characters.

Area A of the continuation line must be blank, or the character-string that is presented across continuation lines is an invalid word in COBOL. The hyphen in the indicator area is ignored.

The program contained within program '@1@' must end with an end program header. An end program header is assumed.

The end program header does not contain a period or it contains an invalid word.

The end program header does not have a program-name.

A character string occurs after the end program header that is not part of another program. The character string is ignored.

Source program must not appear after the end program header of outermost program in library text.

An I/O error occurred while processing the COBOL library text. Processing of the library text was terminated.

The library text cannot include itself.

The COBOL library '@1@' could not be found, or the library has an invalid organization or record format.

Program '@1@' specified in the end program header is missing. The end program header uses the last unterminated program.

The @1@ statement cannot be specified in library text referenced by a COPY statement with a REPLACING or JOINING phrase.

Word @1@ must be preceded by a space and followed by a space.

The @1@ statement is invalid, or the separator period is missing.

A pseudo-text-1 is used that has no text words, or only contains a separator comma and separator semicolon. That pseudo-text-1 is not used as replace object.

The period of the @1@ statement must be followed by a space.

The REPLACE statement must be preceded by a separator period.

The REPLACE statement is invalid or a separator period is missing.

The REPLACE statement corresponding to the REPLACE OFF statement is missing.

An open or close error occurred in the AIM directory data set. The AIM spread record area and special register 'FCOM' are not reserved.

The subschema specified in the SUBSCHEMA-NAME paragraph is missing in the AIM directory data set. The SUBSCHEMA-NAME paragraph is ignored.

The @1@ statement must start in Area B. The statement is assumed to start in Area B.

The first word of the library text copied by a COPY statement after a level 01 or 77 item must be '01' or '77'. The compilation continues.

The text generated by a REPLACE statement execution contains a REPLACE statement.

(CONF)The COPY statement is specified after a level 01 or 77 item.

(CONF)Only '*' is specified as pseudo-text-1 in the COPY statement.

When the NONUMBER option is specified, diagnostic messages relating to COPY statements display the line number of the REPLACE statement rather than that of the COPY statement. Use the NUMBER option to get the exact line number of invalid COPY statements.

The word 'DIVISION' or 'SECTION' is missing. 'DIVISION' or 'SECTION' is assumed to be coded.

In programs included in other programs, the APPLY SAVED-AREA clause must have the ON phrase, and the APPLY MULTICONVERSATION-MODE clause must include a file-name.

The period is missing. The period is assumed to be coded.

The PROGRAM-ID paragraph is missing. The program-name is generated by the system.

The PROGRAM-ID paragraph must be the first paragraph in the IDENTIFICATION DIVISION. The PROGRAM-ID paragraph is assumed to be the first paragraph in the IDENTIFICATION DIVISION.

An invalid character-string is specified in the program-id, or the program-id is missing. The program-name of the next paragraph or division is used.

'COMMON' can only be specified for internal programs.

The program-name '@1@' is already specified in another PROGRAM-ID paragraph or ENTRY statement. Program-name '@1@' ignored.

CONFIGURATION SECTION cannot be specified in an internal program.

The CONFIGURATION SECTION must be specified before the INPUT-OUTPUT SECTION.

The CONFIGURATION SECTION or INPUT-OUTPUT SECTION is already specified.

Each paragraph of the CONFIGURATION SECTION or INPUT-OUTPUT SECTION is already specified.

A FILE-CONTROL paragraph or SELECT clause must be specified before the I-O-CONTROL paragraph.

The CONFIGURATION SECTION header is missing. The header is assumed to be coded.

The INPUT-OUTPUT SECTION header is missing. The header is assumed to be coded.

The syntax of the '@1@' clause is invalid, or the symbolic constant '@2@' is undefined.

An invalid word '@1@' was found. The invalid word and any following code is ignored until the next valid paragraph, section or division.

The @1@ clause is already specified.

A file-name must be specified in the SELECT clause.

The syntax of the @1@ clause is invalid.

The file-name must be specified in the file description entry.

'RECURSIVE' can only be specified for external programs.

The LOCAL-STORAGE SECTION can only be specified for an external program that does not contain the INITIAL attribute.

FILLER cannot be specified after level-number '66', '78', or '88'.

A condition-name must be specified after level-number '88'.

A VALUE clause must immediately follow the condition-name in the condition-name description entry.

A RENAMES clause must immediately follow the data-name in '66' level-number data description entries.

COMMON, INITIAL, or PROTOTYPE is already specified. This COMMON, INITIAL or PROTOTYPE is ignored.

COMMON, INITIAL or RECURSIVE is already specified. This COMMON, INITIAL or RECURSIVE is ignored.

An invalid character is specified in the PICTURE character-string. PICTURE 9 is assumed.

A nonnumeric character cannot be specified in parentheses. PICTURE 9 is assumed.

The numeric in parentheses in the PICTURE character-string is zero or is not a valid numeric. 1 is assumed.

The right parenthesis corresponding to the left parenthesis is missing. PICTURE 9 is assumed.

The numeric in parentheses in the PICTURE clause or consecutive same character length must not exceed 2147483647. 2147483647 is assumed.

CR or DB can be specified only at the end of a PICTURE character-string. PICTURE 9 is assumed.

The END DECLARATIVES corresponding to the DECLARATIVES is missing. An END DECLARATIVES is assumed to be specified.

Level-number 01 or 77 must be specified from area A. The level-number is assumed to be specified from area A.

The integer in the TRACK-AREA clause must not exceed 32760. 32760 is assumed.

The integer in the @1@ clause must not exceed 32767. 32767 is assumed.

The FOOTING, TOP, or BOTTOM operand in the LINAGE clause is invalid.

The data-name in the REDEFINES clause cannot be qualified. The qualifier is ignored.

The syntax is invalid. This syntax is ignored.

Two or more file-names must be specified in a SAME clause. The SAME clause is accepted as written.

The file-identifier '@1@' in the RERUN clause is invalid.

The integer in the RECORDS phrase of the RERUN clause must be between 1 and 2147483647.

The file-name in the @1@ clause is missing or the syntax is invalid.

The syntax of the APPLY clause is invalid.

FILE must be specified in the MULTIPLE FILE TAPE clause. FILE is assumed to be specified.

The syntax of the MULTIPLE FILE TAPE clause is invalid.

An integer must be specified in the POSITION clause of the MULTIPLE FILE TAPE clause.

A period can be specified only at the end of an I-O-CONTROL paragraph. The period is ignored.

The integer in the OCCURS clause must not exceed the value of the integer in the TO phrase. The integer in the TO phrase is used in the OCCURS clause.

If the maximum number of occurrences is specified in the OCCURS clause, a DEPENDING ON phrase must also be specified. The maximum number of occurrences is assumed to be the exact number of occurrences.

The exact or maximum number of occurrences in the OCCURS clause must be greater than or equal to 1. 1 is assumed to be specified.

A file-name must be specified after level indicator SD. This entry ignored, and processing skips to the next division, paragraph, level indicator, or level-number.

A data-name must be specified in the PROCESSING MODE clause of a presentation file.

The @1@ clause can be specified only for a presentation file.

The FORMAT clause can be specified only for a presentation file or a sequential file.

The GROUP clause can be specified only for a presentation file or a print file with a FORMAT clause.

SEQUENTIAL must be specified in the ACCESS MODE clause of a presentation file. SEQUENTIAL is assumed.

The syntax of the MESSAGE MODE, MESSAGE CLASS, MESSAGE OWNER, or MESSAGE CODE clause is invalid.

The literal in the SYMBOLIC CONSTANT clause must be a numeric literal, nonnumeric literal, national literal, Boolean literal, hexadecimal nonnumeric literal, or pointer literal.

Two or more @1@ clauses are specified.

The syntax of the PROGRAM COLLATING SEQUENCE clause is invalid.

The ALPHABET clause must be specified before the SYMBOLIC CHARACTERS clause.

The mnemonic-name is missing from the FUNCTION-NAME clause.

The mnemonic-name or the switch-status condition-name is missing from the FUNCTION-NAME clause with an external switch.

The condition-name is missing from the ON/OFF STATUS clause.

The syntax of the FUNCTION-NAME clause or ALPHABET clause is invalid.

The numeric literal in the ALPHABET or CLASS clause must be between 1 and 256. 1 is the assumed numeric literal for 0. 256 is the assumed numeric literal for values greater than 256.

The nonnumeric literal in the ALPHABET clause must be 1 byte in length. The first byte is used as the nonnumeric literal.

Each native character must be represented by only one literal in the ALPHABET clause.

The syntax of the SYMBOLIC CHARACTERS clause is invalid.

The number of symbolic characters and integers in the SYMBOLIC CHARACTERS clause must correspond.

The integer in the SYMBOLIC CHARACTERS clause must not exceed 256. The integer 256 is used.

The syntax of the CLASS clause is invalid.

The nonnumeric literal must be 1 character in length in a CLASS clause with a THROUGH phrase. The first character is used as the nonnumeric literal.

The syntax of the BLOCK CONTAINS clause is invalid.

The integer in the BLOCK CONTAINS clause exceeds 32760. 32760 is used.

In a BLOCK CONTAINS clause, the smallest block size specified must be less than the greatest block size specified. The greatest block size is assumed to be the same as the smallest block size.

The syntax of the RECORD clause is invalid.

In a RECORD clause data record, the smallest character size must be less than greatest character size. The greatest character size is assumed to be the same as the smallest character size.

An integer must be specified in the RECORD CONTAINS clause.

The syntax of the VALUE clause of the condition-name is invalid.

The syntax of the RENAMES clause is invalid.

The subschema-name must not exceed 8 characters.

The invalid character-string '@1@' is specified as a subschema-name.

The subschema-name is missing.

The syntax of the SUBSCHEMA-NAME paragraph is invalid.

A period is required at the end of the SUBSCHEMA-NAME paragraph.

EXTERNAL or GLOBAL is specified more than once in the SUBSCHEMA-NAME paragraph.

The alphabet-name '@1@' in the SYMBOLIC CHARACTERS clause is undefined.

The alphabet-name in the SYMBOLIC CHARACTERS clause must correspond to STANDARD-1, STANDARD-2, NATIVE, or literal.

The word RECORD or RECORDS is missing from the LABEL RECORDS clause. The word is assumed to be specified.

The SECTION header is missing. The following is assumed: FILE SECTION for FD or SD, REPORT SECTION for rd, or WORKING-STORAGE SECTION for level-number.

A Level 66 item must be specified only after an item with a level-number of 01 through 49, or 66. The Level 66 item is ignored.

A Level 77 item cannot be specified in a FILE SECTION. The item is assumed to be a level 01.

An item with a level-number of 02 through 49 is specified without a level 01 item. The item is assumed to be a level 01.

0 cannot be specified as an integer in the @1@ clause.

The ordinal position corresponding to the integer in the SYMBOLIC CHARACTERS clause does not exist in the specified character set. Assumed to be ordinal position in the native character set.

A section-name is required immediately after DECLARATIVES. The section-name is assumed.

A paragraph-name is specified immediately after a DECLARATIVES. The paragraph-name is used as the section-name.

A section name must be specified immediately in front of the USE statement. The paragraph-name is used as the section-name.

A section-header is required immediately in front of a USE statement.

The alphabet-name '@1@' of the PROGRAM COLLATING SEQUENCE clause must correspond to STANDARD-1, STANDARD-2, NATIVE, or literal.

The alphabet-name '@1@' specified in the PROGRAM COLLATING SEQUENCE clause is undefined.

The ALTERNATE RECORD KEY must not exceed 125.

A qualifier must follow the connective word OF or IN. OF or IN is ignored.

SEPARATE must precede CHARACTER in the SIGN clause. SEPARATE is assumed.

The number of index-names specified for one item must not exceed 60. The first 60 index-names are used.

EXEC @1@ cannot be specified in the CONSTANT SECTION.

The INCLUDE @1@ statement is duplicated.

The syntax of the EXEC AQL statement is invalid.

An END DECLARE SECTION is specified, but no BEGIN DECLARE SECTION is specified.

The END DECLARE SECTION statement is duplicated.

The syntax of the BEGIN DECLARE SECTION statement is invalid.

The syntax of the END DECLARE SECTION statement is invalid.

The integer in the OCCURS clause must not exceed 2147483647. 2147483647 is assumed.

The FILE-CONTROL paragraph is not specified. A FILE-CONTROL paragraph is assumed to be specified.

An I-O-CONTROL paragraph is not specified. an I-O-CONTROL paragraph is assumed to be specified.

A period must end the 'EXEC AQL' statement included in the 'INCLUDE AQLCA' statement.

The alphabet-name specified in the SYMBOLIC CHARACTERS clause is defined multiple times.

The alphabet-name specified in the PROGRAM COLLATING SEQUENCE clause is defined multiple times.

A program-name paragraph must be specified in the IDENTIFICATION DIVISION.

An invalid character-string @2@ is specified as the @1@-name, or the @1@-name is missing.

'@1@' cannot be specified as the data-name after a level-number. win,os4 words before the next level-number are ignored.

The syntax of the @1@ phrase in the OCCURS clause is invalid. The phrases following this phrase in the OCCURS clause are ignored.

An INCLUDE AQLCA statement cannot be specified in an AQL VARIABLE DECLARE SECTION.

An OCCURS clause cannot be specified for a level 01 or level 77 item.

An EXTERNAL clause can be specified only for a file description (FD) entry in a FILE SECTION, or an 01 level item in a WORKING-STORAGE SECTION.

The EXTERNAL clause and the REDEFINES clause cannot be specified for the same data item. The REDEFINES clause is ignored.

The GLOBAL clause can be specified only for a level 01 item in a FILE SECTION, a WORKING-STORAGE SECTION, a CONSTANT SECTION, or a BASED-STORAGE SECTION.

The file control entry requires an ASSIGN clause.

The organization of the ASSIGN clause conflicts with the ORGANIZATION clause. The ORGANIZATION clause is ignored.

The organization of the ASSIGN clause conflicts with the ORGANIZATION clause. The ASSIGN clause is ignored.

For the RDB file, INDEXED must be specified in the ORGANIZATION clause. INDEXED is assumed.

For a sequential file, SEQUENTIAL must be specified in the ACCESS MODE clause. SEQUENTIAL is assumed.

DYNAMIC cannot be specified in the ACCESS MODE clause for a direct organization file, relative organization file, or indexed organization file. RANDOM is assumed.

A RESERVE clause with ALTERNATE or NO can be specified only for sequential, relative organization, indexed organization or direct organization files.

A TRACK-AREA clause can only be specified for an indexed organization file of random access mode.

The TRACK-LIMIT clause can be specified only for a direct organization file.

A FILE STATUS clause cannot be specified for a direct organization file, a relative organization file, or an indexed organization file.

A CONTROL AREA clause can be specified only for a presentation file.

The NOMINAL KEY clause can be specified only for an indexed organization file.

The RELATIVE KEY clause can be specified only for a relative file.

A RELATIVE KEY clause must be specified for a relative file of random or dynamic access mode.

A NOMINAL KEY clause must be specified for an indexed organization file of random access mode.

The RECORD KEY clause can be specified only for an indexed file.

A RECORD KEY clause must be specified for an indexed file.

The ACTUAL KEY clause can be specified only for a direct organization file.

An ACTUAL KEY clause must be specified for a direct file of random access mode.

The ALTERNATE RECORD KEY clause can be specified only for an indexed file.

A DUPLICATES phrase in a RECORD KEY clause can be specified only for an indexed file.

An EXTERNAL clause or a GLOBAL clause cannot be specified for a filler item. The EXTERNAL clause or GLOBAL clause is ignored.

The name in the file-identifier '@1@' is invalid. The file-identifier is ignored.

(CONF)For the LANGLVL(74) option, lower-case 'a' through 'z' can be specified in the CURRENCY SIGN clause as a currency symbol. For the LANGLVL(68) option, lower-case 'a' through 'z' or special-character '/' or '=' can be specified in the CURRENCY SIGN clause as a currency symbol.

(CONF)For the LANGLVL(68) option, the editing character '/' is ignored.

(CONF)Special register SORT-STATUS is specified in the PROCEDURE DIVISION.

(CONF)The PROGRAM-ID paragraph is not specified, or an invalid program-name is specified. A 'NOPRGMID' program-name is assumed.

(CONF)An alphabet-name having a CONSTANT phrase with ALSO is specified in a PROGRAM COLLATING SEQUENCE clause and a figurative constant HIGH-VALUE or LOW-VALUE is referenced.

The syntax of the WITH DEBUGGING MODE clause is invalid.

The integer of the TRACK-AREA clause must be a multiple of 8. The integer is truncated to a multiple of 8.

A level 88 item must be specified after an item with level 01 to 49 or 77. The level 88 item is ignored.

The invalid word '@1@' is specified in the IDENTIFICATION DIVISION. The invalid word is ignored, and the compiler skips to the next paragraph or DIVISION.

The data-name must be specified immediately after level-number 66.

The REDEFINES clause must be the first clause in the data description entry. The REDEFINES clause is assumed to be valid.

'@1@' cannot be specified as the currency symbol.

An unsigned integer, nonnumeric literal, or figurative constant must be specified in the THROUGH or ALSO phrase of an ALPHABET clause. The alphabet name '@1@' is ignored.

The organization in the file-identifier '@1@' is invalid. The file-identifier is ignored.

When a device class in a file-identifier is PTR or PTP, the organization must be 'S'. The device class is ignored.

The database-name or table-name in the file-identifier '@1@' is invalid.

The record format 'U' cannot be specified for a sort-merge file.

An invalid word '@2@' is specified immediately after level number '@1@'. It is assumed that this data description has no name.

A level item of 02 to 49 cannot be specified immediately after a 66 level item. A level item of 01 is assumed.

The mnemonic-name is missing after 'IS' in the FUNCTION-NAME clause. 'IS' is ignored.

The BASED ON clause can be specified only for a level 01 or 77 item in the BASED-STORAGE SECTION.

The REDEFINES clause and the BASED ON clause cannot be specified for the same data item. The BASED ON clause is ignored.

The syntax of the SYMBOLIC CONSTANT clause is invalid.

The literal in the SYMBOLIC CONSTANT clause must be a numeric literal, a nonnumeric literal, a national literal, a Boolean literal, or a hexadecimal nonnumeric literal.

The symbolic constant '@1@' is not unique.

The symbolic constant '@1@' cannot be specified in the '@2@' clause.

The GLOBAL clause can be specified only for a level 01 item in the BASED-STORAGE SECTION, FILE SECTION, WORKING-STORAGE SECTION, CONSTANT SECTION, or LINKAGE SECTION.

The PICTURE character-string must be 1 through 18 digit positions. PICTURE 9 is assumed.

The PICTURE character-string must be 1 through @1@ digit positions. PICTURE 9 is assumed.

The symbols S, V, '.', CR, and DB can appear only once in the PICTURE character-string. PICTURE 9 is assumed.

The symbol 'S' must appear as the leftmost character in the PICTURE character-string. PICTURE 9 is assumed.

'P' is specified at an invalid position in the PICTURE character-string. PICTURE 9 is assumed.

The symbols '+', '-', '*', 'Z', and the currency symbol, when used as floating replacement characters, are mutually exclusive in a PICTURE character-string. PICTURE 9 is assumed.

A floating insertion character or a zero suppression character cannot be preceded by a '9' in the PICTURE character-string. PICTURE 9 is assumed.

Only one kind of character can be used to specify digit positions to the right of the decimal point in a PICTURE character-string. PICTURE 9 is assumed.

The symbols '+', '-', 'CR', and 'DB' are mutually exclusive in a PICTURE character-string. PICTURE 9 is assumed.

A decimal point cannot be specified with a 'V' or 'P' in a PICTURE character-string. PICTURE 9 is assumed.

The length of a numeric edited item must not exceed 160 bytes. PICTURE 9 is assumed.

A fixed insertion character '+', '-' or currency symbol is specified at an invalid position in the PICTURE character-string. PICTURE 9 is assumed.

The number of digits in the mantissa must be from 1 to 16 when specifying the PICTURE character-string for an external floating-point item. PICTURE +9.E+99 is assumed.

A sign must be specified for both the mantissa and exponent in the PICTURE character-string for an external floating-point item. A plus sign '+' is assumed.

Only one 'E' can be specified in a PICTURE character-string. PICTURE +9.E+99 is assumed.

2 digit positions must be specified for the exponent in a PICTURE character-string of an external floating-point item. 2 digits are assumed.

A 'V' or a decimal point must be specified for the mantissa in a PICTURE character-string of an external floating-point item. A 'V' is assumed after the last digit of the mantissa.

The PICTURE character-string of the external floating-point item is invalid. PICTURE +9.E+99 is assumed.

An invalid combination is specified in the PICTURE character-string. PICTURE 9 is assumed.

The number defining the number of occurrences of a character in a PICTURE character-string must not exceed 10 digits in length. The first 10 digits are used.

National items and national edited items must not exceed 1073741823 characters in length. 1073741823 characters is assumed.

Elementary items must not exceed 2147483647 bytes in length. 2147483647 bytes is assumed.

When all of the characters indicating numeric digit positions are floating insertion characters, at least one of them must be specified to the left of the decimal point in the PICTURE character-string of the numeric edited item.

The SEGMENT-LIMIT clause and the segment-number in the section header are assumed to be a comment.

An END DECLARE SECTION statement must be specified at the end of the AQL VARIABLE DECLARE SECTION. An END DECLARE SECTION statement is assumed at the end of the section.

Only the following AQL statements can be specified for the WORKING-STORAGE SECTION and the LINKAGE SECTION: BEGIN DECLARE SECTION, END DECLARE SECTION, INCLUDE AQLCA.

The BEGIN DECLARE SECTION statement is duplicated in the section.

When the device class is 'SP' in a file-identifier, 'S' must be specified in the organization. The file-identifier is ignored.

A SQL statement and an AQL statement must not be written in a separately compiled program. The @1@ statement is ignored.

A character not in the national character set is used in a national user-defined word. The user-defined word is ignored.

The program-name exceeds 30 characters. The first 30 characters are assumed to be program-name.

In this system, '@1@' is assumed to be a comment.

The concatenation expression is too long. A literal is created using the first parts of the expression so that it does not exceed the maximum length.

A nonnumeric literal, national literal or figurative constant must be specified after '&'. A combination of literals in a concatenation expression is invalid. '&' is ignored.

'@1@' is a function specific to the MSP or XSP system.

The length of the host identifier qualification in an alphanumeric character exceeds in embedded 250 characters. The first 250 characters are accepted.

A tab is included in a literal. The tab is accepted as code.

When a literal is continued across lines, the first nonblank character of the continuation line must be a quotation mark, and the continued line must be terminated by a quotation mark followed by a hyphen.

When a literal is continued across lines, at least one character position in the content of the literal must be specified on the continued line and on each continuation line.

The ending quotation mark of the literal is missing. The characters to end of the program-text area are assumed to be the literal.

When the compilation option ENCODE(UTF8,UTF16) or ENCODE(UTF8,UTF32) is specified, then in the concatenation expression, national hexadecimal, a nonnumeric literal cannot be defined. The concatenation expression will be disabled.

In the TYPE clause, HEADING or FOOTING must be specified immediately after REPORT, PAGE, or CONTROL.

0 cannot be specified as the integer in the COLUMN NUMBER clause. 1 is assumed.

The integer in the COLUMN NUMBER clause must not exceed 32767. 32767 is assumed.

Data-name or FINAL must be specified for RESET in the SUM clause. RESET is ignored.

A data-name must be specified for UPON in the SUM clause. UPON is ignored.

A report-name must be specified immediately after the connective word OF or IN of PAGE-COUNTER or LINE-COUNTER in a SOURCE clause. OF or IN is ignored.

The nonnumeric literal in the CODE clause must be 2 characters. If the nonnumeric literal is 1 character, then the second byte is assumed to be blank. Otherwise, the first 2 characters are accepted.

The integer of the PAGE LIMIT clause must not exceed 999. 999 is assumed.

0 cannot be specified as an integer in the PAGE LIMIT clause. 999 is assumed.

The syntax of the PAGE clause is invalid.

In the PAGE clause, an integer must be specified immediately after HEADING, FIRST DETAIL, LAST DETAIL, or FOOTING.

In the PAGE clause, DETAIL must be specified immediately after FIRST or LAST. The PAGE clause description after FIRST or LAST is ignored.

The integers in the PAGE clause must be in following order: HEADING, FIRST DETAIL, LAST DETAIL, FOOTING, PAGE LIMIT. Only the integer specified in PAGE LIMIT is assumed to be valid.

The integer in the @1@ phrase must not exceed 999, and must not be 0.

'@1@' is already specified in the PAGE clause.

The syntax of the LINE NUMBER clause is invalid.

The integer in the @1@ clause must not exceed 999. 999 is assumed.

ON NEXT PAGE is invalid in the LINE NUMBER clause. ON NEXT PAGE is ignored.

The integer 0 cannot be specified in the NEXT GROUP clause.

The NEXT GROUP clause is already specified.

DISPLAY must be specified in the USAGE clause of the report group description entry. DISPLAY is assumed.

A report group description entry is specified with only a level-number or with only a level-number and a data-name. Compilation continues.

The @1@ clause can be specified only for a report group description entry of level-number 01.

SEPARATE CHARACTER must be specified in the SIGN clause.

The BLANK WHEN ZERO clause cannot be specified in a report group description entry with a VALUE clause.

Only one of the clauses SUM, SOURCE, or VALUE can be specified in a report group description entry. The first clause in the entry is used.

Only one of the clauses COLUMN NUMBER or PRINTING POSITION can be specified in a report group description entry. The first clause in the entry is used.

The report-name is missing from the report description entry.

An EXTERNAL clause cannot be specified in a report description entry.

FILLER cannot be specified in a report group description entry.

Level-number 66, 77, 78, and 88 cannot be specified in a report group description entry.

The level-number of the report group description entry must be specified in the range of 3 levels. The correct level is assumed.

The LINAGE clause cannot be specified in a file description entry with a REPORT clause.

The GLOBAL clause cannot be specified in a report description entry.

In the PADDING CHARACTER clause, the nonnumeric literal must be 1 character in length. A 1 character length is assumed.

The @1@ clause can be specified only for a sequential file.

(OBS)The @1@ clause is an obsolete element in @2@ COBOL.

(OBS)The @1@ paragraph is an obsolete element in @2@ COBOL.

The PASSWORD clause can be specified only for a sequential file (organization AS or VS), a relative file, or an indexed file.

The END DECLARE SECTION is missing. An END DECLARE SECTION is assumed.

Only a BEGIN DECLARE SECTION and an END DECLARE SECTION can be specified in the WORKING-STORAGE SECTION or the LINKAGE SECTION.

Only a BEGIN DECLARE SECTION and an END DECLARE SECTION can be specified in the WORKING-STORAGE SECTION, the LOCAL-STORAGE SECTION or the LINKAGE SECTION.

(OBS)@1@ is an obsolete feature in @2@ COBOL.

The name in the literal '@1@' specified for the ASSIGN clause is invalid.

The name in the literal '@1@' specified for the ASSIGN clause exceeds 44 characters.

The integer in the POSITION phrase of the MULTIPLE FILE TAPE clause must not exceed @1@. @1@ is assumed.

END-EXEC of the INCLUDE @1@ statement must end with a period.

The INCLUDE @1@ statement cannot be specified in the EMBEDDED SQL DECLARE SECTION.

The PASSWORD clause must be specified in the RECORD KEY or ALTERNATE RECORD KEY clause.

The integer in the HAVING phrase must be between 1 and 33554431.

The syntax of the INCLUDE SQLDA statement is invalid.

The SQLDA structure name in the INCLUDE SQLDA statement is invalid.

The syntax of the @1@ clause is invalid.

The literal of the POSITIONING UNIT clause must be an unsigned numeric literal with a value of 0.01 through 24.00. The number of decimal digits cannot exceed 2.

The positioning-unit-name must be specified for the BY phrase in the PRINTING POSITION clause.

A printing-mode-name must be specified immediately after the OR phrase in the CHARACTER TYPE clause.

A data-name must be specified for the DEPENDING ON phrase in the CHARACTER TYPE clause.

When two or more printing-mode-names are specified in a CHARACTER TYPE clause, a DEPENDING ON phrase must be specified.

The @2@ phrase in the @1@ clause is invalid.

The @2@ phrase is already specified in the @1@ clause.

The literal in the SIZE phrase must be an unsigned numeric literal with a value of 3 through 300. The number of decimal digits must not exceed 1.

The literal in the PITCH phrase must be an unsigned numeric literal with a value of 0.01 through 24.00. The number of digit digits must not exceed 2.

The integer in the ANGLE phrase must be 0 or 90.

The function-name of the @1@ phrase is invalid.

@1@ cannot be used in this system.

PRINTER in the ASSIGN clause can be specified only in a sequential file other than a line sequential file.

MANUAL in the LOCK MODE clause can be specified only in a relative or indexed file.

Each level 01 item must have a data-name.

The integer in the BACKGROUND-COLOR or FOREGROUND-COLOR clause must be a value from 0 through 7.

DISPLAY must be specified in the USAGE clause of the screen description entry. DISPLAY is assumed.

The JUSTIFIED clause cannot be specified in a screen description entry with a FULL clause. The JUSTIFIED clause is ignored.

The '@1@' clause and the '@2@' clause cannot both be specified in the same screen description entry. The '@2@' clause is ignored.

The '@1@' phrase and the '@2@' phrase cannot both be specified in the same PICTURE clause.

Only a nonnumeric literal or a national literal can be specified in the VALUE clause of a screen description entry.

Each screen description entry must start with a level number of 01 through 49, or 78.

The LOCK MODE clause can only be specified in a file that is sequential, relative, or indexed.

In the SCREEN SECTION, the PICTURE clause must be specified in the item which has a FROM, TO or USING phrase.

'@2@' must be specified in a '@1@' clause.

An '@3@' must be specified in a '@1@' clause with a '@2@' phrase.

DISK or PRINTER in an ASSIGN clause cannot be specified in a print file with a FORMAT clause.

'@1@' is a proper function to the MSP or XSP system.

The @1@ clause can only be specified for a level 01 item in the SCREEN SECTION.

@1@ cannot be specified for a PROGRAM DEFINITION that contains the RECURSIVE attribute.

A comment-entry cannot be connected using a hyphen in an indicator area. The hyphen is ignored.

The function-name of the function is invalid or missing.

(CONF)Character string following the left parenthesis in the library text is replaced.

Not able to access the working area of memory of the referenced library.

An incomplete FFD or MED is specified.

The MED exceeds the maximum size of data that can be processed. Reduce the size of this MED in the environment where it was created.

The program for expanding FFD or MED cannot be loaded or deleted.

The input-output item is not defined in FFD or MED.

National hexadecimal literals must consist of hexadecimal characters (0 through 9, a through f). The national literal is assumed to be a space.

An I/O error occurred while reading the library text. Reading the library text is terminated.

A national literal contains characters that cannot be converted to a national character. The national literal is assumed to be a space.

An FFD file descriptor or an MED screen form descriptor that uses an unsupported function is specified.

The @1@ cannot be specified in a @2@. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

A @2@ can only be specified in a @1@ clause. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

@1@ cannot be specified in a @2@. It is ignored, and the compiler skips to the next paragraph or division.

The @1@ clause can only be specified in the WORKING-STORAGE SECTION of the FACTORY or OBJECT definition. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

The @1@ clause cannot be specified in a @2@. It is ignored, and the compiler skips to the next valid clause, paragraph, section, or division.

The GET or SET phrase of the PROPERTY clause must be specified with 'NO'. It is ignored, and the compiler skips to the next valid clause, paragraph, section, or division.

The 'NO' of the PROPERTY clause must be specified with a GET or SET phrase. It is ignored, and the compiler skips to the next valid clause, paragraph, section, or division.

The PROPERTY clause cannot be specified for a filler item. The PROPERTY clause is ignored.

A @2@ can only be specified in a @1@.

A @1@ cannot be specified in a @2@. It is ignored, and the compiler skips to the next paragraph, section or division.

MULTIPLE REEL and UNIT phrases can only be specified in the PROGRAM definition.

'@1@' is a proper function to the MSP or XSP system.

@2@ can only be specified in @1@. It is ignored, and the compiler skips to the next END-EXEC, section or division.

@1@ can only be specified in the PROGRAM definition, OBJECT definition or OBJECT METHOD definition. It is ignored, and the compiler skips to the next END-EXEC, section or division.

The @1@ clause can only be specified in a level-number '01' item. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

The named-constant name must be specified after level-number '78'. This entry is ignored, and the compiler skips to the next division, paragraph, level indicator or level-number.

The named-constant description entry can only specify a VALUE clause. This entry is ignored, and the compiler skips to the next division, paragraph, level indicator or level-number.

Level-number '78' cannot be specified in a @1@. This entry is ignored, and the compiler skips to the next division, paragraph, level indicator or level-number.

The ANY LENGTH clause can only be specified in level-number '01' of the METHOD definition LINKAGE SECTION. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

The character in the PICTURE clause must be specified as one character for 'X' or 'N'. The ANY LENGTH clause is ignored.

The @1@ clause cannot be specified for a filler item. The @1@ clause is ignored.

The period is missing in @1@, or an invalid word is used.

The @2@ is missing from the @1@.

The @2@ cannot inherit from itself.

The inherited @1@ is missing. The INHERITS clause is ignored.

@1@ is already specified. @1@ is ignored.

The @3@ '@1@' specified by the @2@ is missing. The @2@ assumed to refer to the last non-terminated @3@.

An invalid character-string is specified in the PROGRAM-ID, or the PROGRAM-ID is missing. The @1@ from the next paragraph or division is used.

(CONF)A @1@ is not specified, or an invalid @2@ is specified. A '@3@' @2@ is specified.

The @1@ phrase cannot be specified for SEPARATED METHOD. The @1@ phrase is ignored.

A class-name can only be specified for a SEPARATED METHOD. The class-name is ignored.

The syntax of the PROPERTY phrase is invalid. The PROPERTY phrase is ignored.

The syntax of the property-specifier is invalid.

A @1@ paragraph can only be specified in the PROGRAM definition. It is ignored until the next paragraph or division.

CLASS '@1@' must end with an end class header. An end class header is assumed.

The @1@ is missing. An @1@ is assumed.

The position of the @1@ is invalid. The @1@ is ignored, and the compiler skips to the next element.

The invalid word '@1@' was found. The invalid word is ignored and the compiler skips to the next element.

The @1@ is already specified. The compiler skips to the next element.

The @1@ clause must be the first clause in the data description entry. The @1@ clause is assumed to be valid.

No corresponding end header is specified. The end header is ignored.

The separated method must be the specified class-name for the prototype method defined class. The compiler skips to the next element.

The end method header for a method defined with GET or SET in the METHOD-ID paragraph must omit the method-name.

No corresponding end header is specified. The compiler skips to the next element.

A literal cannot be specified for a class-name, method-name, delegate-name, ENUM-name, or interface-name.

The repository file for CLASS '@1@' is not allocated. The compiler skips to the next element.

The repository file of CLASS '@1@' is invalid. The compiler skips to the next element.

The repository file of CLASS '@1@' is not allocated.

The repository file of CLASS '@1@' is invalid.

The repository file of CLASS '@1@' does not have information for the PROTOTYPE METHOD. The compiler skips to the next element.

The inherited @1@ '@2@' is not specified in the REPOSITORY paragraph, or the @1@-data cannot be restored. The INHERITS clause is ignored.

The PROTOTYPE METHOD defined in CLASS '@1@' is not specified in the REPOSITORY paragraph. The compiler skips to the next element.

METHOD '@1@' is multi-defined. METHOD '@1@' is ignored.

Inherited same name METHOD '@1@' must have the same interface.

The @1@ '@2@' is already specified in the REPOSITORY paragraph.

The syntax of the special CLASS is invalid.

The syntax of the @1@-specifier is invalid.

The CLASS '@2@' referenced by object reference data item @1@ is not specified in the REPOSITORY paragraph. It is assumed to be a universal object reference data item.

The definition name of the source that is currently being compiled cannot be specified in the REPOSITORY paragraph.

The inherited @1@ must be specified in the REPOSITORY paragraph. The INHERITS clause is ignored.

The PROTOTYPE METHOD defined in the CLASS must be specified in the REPOSITORY paragraph. The compiler skips to the next element.

Special CLASS @1@ cannot be inherited. CLASS '@1@' is ignored.

Special CLASS '@1@' cannot be defined in a PROTOTYPE METHOD. CLASS '@1@' is ignored.

The repository data cannot be restored. The compilation was terminated. Correct the other reported errors and try the compilation again.

The CLASS '@1@' specified in the REPOSITORY paragraph must have the same specifier when defined in the PROTOTYPE METHOD. CLASS '@1@' is ignored.

The repository file for the CLASS '@1@' that defined the PROTOTYPE METHOD must be created with the same VL compiler. The compiler skips to the next element.

The format of the repository file for CLASS '@1@' is invalid for this compiler. CLASS '@1@' is ignored.

Method names starting with '@1@' are reserved for the COBOL system. To use such method names, the OVERRIDE phrase must be specified. It is accepted as written.

The first character of the property name cannot be a '@1@'. The PROPERTY phrase is ignored.

The PROPERTY clause cannot be specified if the data name begins with a '@1@'. The PROPERTY clause is ignored.

The parent CLASS '@1@' contains a method name starting with '@2@'. The parent CLASS '@1@' should be recompiled. It is accepted as written.

The AS phrase cannot be specified in internal programs. The compiler skips to the next paragraph or division.

A nonnumeric literal or a national literal must be specified after an AS phrase. The compiler skips to the next paragraph or division.

A nonnumeric literal or a national literal must be specified after an AS phrase. The compiler skips to the next valid clause, paragraph, section or division.

The repository file for CLASS '@1@' was created with the 'CREATE(REP)' compiler option. It cannot be used for a CLASS defining a PROTOTYPE METHOD. The compiler skips to the next element.

The repository file for the parent CLASS cannot be restored. The INHERITS clause is ignored.

The type library does not exist in the specified place.

A type library is not specified for the COM server name in the translation option file, or an error was found in the specified name.

An error was caused by the load type library.

The specified class name does not exist in the type library, or it is an attribute that cannot be used with the acquired type.

An error occurred when acquiring information on the CLASS.

The compile option ENCODE and RCS of CLASS '@1@' must match a current valid source definition compile option. The compilation will continue after this message.

The nonnumeric literal in the @1@ clause cannot contain national characters. It is assumed to be a space.

'DEFINITION' and 'REFERENCE' cannot specify the EXTERNAL clause when compiler option 'THREAD(MULTI)' and 'NOSHREXT' are being used. 'DEFINITION' or 'REFERENCE' is ignored.

A @2@ must be specified in the @1@ phrase.

A @2@ can only be specified in a @1@. It is ignored until the next valid paragraph, section or division.

The length of a hexadecimal numeric literal cannot be zero. Assumed to be a zero.

Hexadecimal numeric literals must have an even number of characters. A zero is added as the first character.

The subschema descriptor file in the SUBSCHEMA-NAME paragraph is incorrect. The SUBSCHEMA-NAME paragraph is ignored.

The syntax is invalid. @1@ assumed valid.

When compiling a program that is embedded with file name control information (#FILE information) and line number control information (#LINE information), then specify compilation option NONUMBER.

In the ENCODING clause, the alphabet name for the encoding format was not defined. The ENCODING clause is disabled.

In the ENCODING clause, the alphabet name for the @1@ specification was already defined. The alphabet name initially defined remains.

The alphabet name defined in the ENCODING clause was defined multiple times. The ENCODING clause is disabled.

The ENCODING clause must have a valid screen form descriptor name in the COPY statement. The ENCODING clause is disabled.

When @1@ is enabled, in the ENCODING clause, alphabet name with encoding @2@ must be specified. The ENCODING clause is disabled.

When UTF32 Encoding format is specified in the screen form descriptor, then there is a need to specify the screen form descriptor that is converted for UTF32. Stop the inclusion of the screen form descriptor.

@2@ cannot be used when compile option @1@ are valid.

The level-number hierarchy is invalid.

The integer in the RECORD clause must not exceed 2147483647. 2147483647 is assumed.

This program cannot be compiled with compile option 'OPTIMIZE' due to insufficient main storage. Compile option 'NOOPTIMIZE' is assumed.

The 'END DECLARE SECTION' corresponding to the 'BEGIN DECLARE SECTION' is missing. This statement is ignored and the DECLARE SECTION is continued.

The report description entry requires a report group description. The report description entry is ignored.

The file description entry or sort-merge file description entry requires a record description. The file description entry or sort-merge file description entry is ignored.

A record description entry cannot be specified for a file description entry with a REPORT clause. The record description entry is ignored until the next file description entry or sort-merge file description entry.

The length of redefining item with an EXTERNAL clause cannot exceed the length of the item with an EXTERNAL clause. It is accepted as written.

When a SYNCHRONIZED clause is specified for an elementary item with a REDEFINES clause or a first elementary item that is a part of a group that contains a REDEFINES clause, the boundary of the redefined item must be adjusted to correct the boundary of the elementary item. The boundary is not adjusted.

The file-name for the file description entry or the sort-merge file description entry must be defined at the SELECT clause of the FILE-CONTROL paragraph. A sequential file is assumed.

The file-name in the SELECT clause must be a unique file-name in the description entry of FD or SD.

The file-name in the SELECT clause must not be same as the file-names in other SELECT clauses.

When the SIGN clause is specified for a group item, at least one signed external decimal item must be specified for subordinating elementary items. The SIGN clause is ignored.

The '@1@' of the USAGE clause cannot be specified for an item with a PICTURE clause.

The USAGE clause for items subordinate to the group item must be of same format as the USAGE clause for the group item. The USAGE clause specified for the group item is used.

A BIT phrase can only be specified for a Boolean item.

BINARY, COMPUTATIONAL, COMPUTATIONAL-3, or PACKED-DECIMAL must be specified for a numeric item.

The SIGN clause can be specified for a signed external decimal item or a group item.

The JUSTIFIED clause cannot be specified for a group item.

The JUSTIFIED clause can only be specified for an alphabetic, alphanumeric, or national item.

A REDEFINES clause cannot be specified for an item with level number 01 in the file section. The REDEFINES clause is ignored.

An item redefined by the REDEFINES clause is not defined correctly.

The @1@ clause cannot be specified for an item redefined by the REDEFINES clause. The REDEFINES clause is ignored.

If an item redefined by a REDEFINES clause is an internal Boolean item without a SYNCHRONIZED clause, the redefining item must also be an internal Boolean item.

The VALUE clause cannot be specified for a data description entry in a based-storage section. The VALUE clause is ignored.

The VALUE clause cannot be specified for a data description entry in a FILE SECTION or LINKAGE SECTION. The VALUE clause is ignored.

The VALUE clause cannot be specified for an @1@ item.

The numeric literal of the VALUE clause specifies a value which is truncated to zero. Figurative constant ZERO is assumed.

A signed numeric literal cannot be specified for an unsigned numeric item. The sign of the numeric literal is ignored.

A nonnumeric literal, figurative constant, or symbolic character must be specified in the VALUE clause of a group item. The figurative constant 'SPACE' is assumed.

A numeric literal or figurative constant 'ZERO' must be specified in the VALUE clause of an internal floating-point item. The figurative constant 'ZERO' is assumed.

Length of the literal in the VALUE clause must not exceed the length of the item. The extra characters at the right end of the literal are truncated.

A numeric literal or figurative constant 'ZERO' must be specified in the VALUE clause of a numeric item. Figurative constant 'ZERO' is assumed.

A nonnumeric literal, figurative constant, or symbolic character must be specified in the VALUE clause of an alphabetic item, alphanumeric item, alphanumeric edited item, or numeric edited item. The figurative constant 'SPACE' is assumed.

If the VALUE clause is specified for a numeric item following 'P', the value of the character position corresponding with 'P' of the numeric item must be zero. The value of the character position corresponding with 'P' of the numeric item is assumed to be zero.

A boolean literal or figurative constant ZERO must be specified in the VALUE clause of a boolean item. Figurative constant ZERO is assumed.

A Boolean literal cannot be specified in the VALUE clause of an alphabetic, alphanumeric, or alphanumeric edited item. Each Boolean character is assumed to be 1 bit, and is stored left-aligned.

The length of a Boolean literal in an alphabetic, alphanumeric, or alphanumeric edited item must be a multiple of 8. The Boolean character '0' is added to the right of the specified literal until its length is a multiple of 8.

National literal or figurative constants SPACE, HIGH-VALUE, or LOW-VALUE must be specified in the VALUE clause of a national item. The figurative constant 'SPACE' is assumed.

The @1@ clause and the SYMBOLIC DESTINATION clause with @2@ are specified for a presentation file. The @1@ clause is ignored.

The @1@ clause cannot be specified when a SYMBOLIC DESTINATION clause with @2@ is specified for the presentation file.

Data-name '@2@' of the @1@ clause is not unique. The @1@ clause is ignored.

Data-name '@2@' of the @1@ clause is undefined. The @1@ clause is ignored.

'@2@' in the @1@ clause must be a data-name. The @1@ clause is ignored.

OMITTED can only be specified in the LABEL RECORD clause for a sequential file. The LABEL RECORD clause is ignored.

A LABEL RECORD clause with a data-name can only be specified for a sequential, direct organization, or relative organization file.

'RECORD CONTAINS 0' can only be specified for a sequential file. The RECORD CONTAINS clause is ignored.

The alphabet-name in the CODE-SET clause is undefined.

The alphabet-name in the CODE-SET clause must correspond to STANDARD-1, STANDARD-2, NATIVE or function-name.

The CODE-SET clause can only be specified for a sequential file.

The format of the CHARACTER TYPE clause for items subordinate to the group item must have the same format as the CHARACTER TYPE clause for the group item. The format of the CHARACTER TYPE clause specified for group item is used.

The mnemonic-name in the CHARACTER TYPE clause is undefined or multi-defined, or the mnemonic-name is not related to the function-name HSC, F0202, H0202, F0102, or F0201. The mnemonic-name is ignored.

The mnemonic-name of the CHARACTER TYPE clause with MODE-3 must be related to F0202, F0102, or F0201.

The file-name '@2@' in the @1@ clause is undefined or multi-defined.

The name '@2@' of the @1@ clause must be the file-name. That specification is ignored.

File-name '@2@' must only be specified once in the @1@ clause of that format. The file-name is ignored.

A signed numeric literal cannot be specified in the VALUE clause of a condition-name related to a conditional variable with an unsigned numeric literal. The unsigned numeric literal is assumed.

The Boolean literal or figurative constant 'ZERO' must be specified in the VALUE clause of the condition-name related to the Boolean item. The figurative constant ZERO is assumed.

In the numeric literal of the VALUE clause, the character position corresponding to the picture character 'P' of the conditional variable must be '0'. The figurative constant ZERO is assumed.

The length of the literal in the VALUE clause for the condition-name must not exceed the item length of the condition variable. Excess characters at the right end of the specified literal are discarded.

Nonnumeric literal, figurative constant or symbolic-character must be specified in VALUE clause of condition-name for conditional variable of alphabetic, alphanumeric, alphanumeric edited, numeric edited, or group item. Figurative constant 'SPACE' assumed.

The figurative constant ZERO cannot be specified in the VALUE clause of the condition-name for the conditional variable of the alphabetic item. The figurative constant SPACE is assumed.

The numeric literal or figurative constant ZERO must be specified in the VALUE clause of the condition-name for the conditional variable of the numeric item. The figurative constant ZERO is assumed.

A Boolean literal cannot be specified in the VALUE clause of the condition-name for the conditional variable of an alphabetic, alphanumeric, alphanumeric indexed, or group item. Each Boolean character is assumed to be 1 bit, and is stored left-aligned.

The length of the Boolean literal in the VALUE clause of the condition-name must be a multiple of 8. The Boolean character '0' is added on the right of the literal until its length is a multiple of 8.

The value of the literal following 'THROUGH' in the VALUE clause of the condition-name must be greater than the value of the literal preceding 'THROUGH'.

A national literal or figurative constants 'SPACE', 'HIGH-VALUE', or 'LOW-VALUE' must be specified in the VALUE clause of the condition-name for the conditional variable of the national item. The figurative constant 'SPACE' is assumed.

A Boolean literal cannot be specified in the VALUE clause of the condition-name with 'THROUGH'.

'RECORD CONTAINS 0' cannot be specified for the file description entry of the file specified in the SAME RECORD AREA clause. The RECORD clause is ignored.

'RECORD CONTAINS 0' cannot be specified for a print file. The RECORD clause is ignored.

The integer (maximum number of character positions) in the RECORD clause must be equal to or greater than the record length. The RECORD clause is ignored.

The integer (minimum number of character positions) in the RECORD clause must be equal to or less than the record length. The RECORD clause is ignored.

A level 01, 77, 88, or 66 item cannot be specified in the RENAMES clause.

The data-names in the RENAMES clause must be different from each other.

The data-name in the RENAMES clause or THROUGH phrase must be defined in the record description entry immediately before that clause.

The data-name in the RENAMES clause or THROUGH phrase cannot have an OCCURS clause, and cannot be subordinate to a data item with an OCCURS clause.

The beginning of the THROUGH phrase data-name area must not be to the left of the beginning of the RENAMES clause data-name area.

A variable occurrence data item must not appear between the data-name in the RENAMES clause and the data-name in the THROUGH phrase.

The data-name in the RENAMES clause with a THROUGH phrase must not be an internal Boolean item.

The character-string in the PICTURE clause conflicts with the USAGE clause of its group item. The character-string in the PICTURE clause is assumed to be valid.

The PICTURE clause cannot be specified for a group item.

The CHARACTER TYPE clause is invalid for group items that do not contain a national item.

The record description entry containing an item with a character type cannot have an item with the OCCURS DEPENDING ON phrase.

The level 01 item must not exceed @1@ bytes in length.

File-name '@1@' in the MULTIPLE FILE TAPE clause must be a sequential file.

If a file in the SAME AREA clause is specified in the SAME RECORD AREA clause, all other file-names in that SAME AREA clause must be specified in that SAME RECORD AREA clause.

The BLANK WHEN ZERO clause cannot be specified for a numeric edited item with an asterisk. The BLANK WHEN ZERO clause is ignored.

The BLANK WHEN ZERO clause can only be specified for an external decimal item or a numeric edited item.

The integer in the RESERVE clause must be specified for a sequential (organization VS or AS), relative, or indexed file. The RESERVE clause is ignored.

The integer in the RESERVE clause must not equal 0 or exceed 255. The RESERVE clause is ignored.

Data-name in PADDING CHARACTER clause must not be defined in FILE SECTION and REPORT SECTION.

The data-name in the PADDING CHARACTER clause must be an alphanumeric or group item.

The data-name in the PADDING CHARACTER clause must be 1 byte in length.

The data-name in the @1@ clause must be a fixed-length item.

The data-name in the @1@ clause must be defined in a record of the file.

The data-name in the @1@ clause must not exceed @2@ bytes in length.

The data-name of the @1@ clause must be an 8-digit binary item.

The figurative constant ZERO cannot be specified in the VALUE clause of an alphabetic item. The figurative constant SPACE is assumed.

The data-name in the RELATIVE KEY clause must be defined in the WORKING-STORAGE, LINKAGE, or FILE SECTION.

The data-name in the RELATIVE KEY clause must be defined in the WORKING-STORAGE, LOCAL-STORAGE, LINKAGE, or FILE SECTION.

The data-name in the RELATIVE KEY clause must not be defined in a record of that file.

The data-name in the RELATIVE KEY clause must be an unsigned integer item without the symbol 'P'.

Data-name '@1@' in the APPLY SAVED-AREA clause must be defined in the WORKING-STORAGE SECTION. The data-name is ignored.

Data-name '@1@' in the APPLY SAVED-AREA clause must be a level-number 01 or 77 item. The data-name is ignored.

Data-name '@1@' in the APPLY SAVED-AREA clause must be a fixed length item. The data-name is ignored.

Data-name '@1@' in the APPLY SAVED-AREA clause must not exceed 32763 bytes in length. The data-name is ignored.

The data-name in the RECORD clause must be defined in the WORKING-STORAGE or LINKAGE SECTION. The data-name is ignored.

The data-name in the RECORD clause must be defined in the WORKING-STORAGE, LOCAL-STORAGE or LINKAGE SECTION. The data-name is ignored.

The data-name in the RECORD clause must be an unsigned integer item. The data-name is ignored.

Data-name '@2@' in the @1@ clause must be unique. The data-name is ignored.

Data-name '@2@' in the @1@ clause is undefined. The data-name is ignored.

'@2@' in the @1@ clause is not defined as a data-name. The data-name is ignored.

Data-name '@1@' in the LINAGE clause must be defined in a section other than the REPORT SECTION. The data-name is ignored.

Data-name '@1@' in the LINAGE clause must be an unsigned integer item. The data-name is ignored.

A named-constant can only be referenced in a FILE SECTION, WORKING-STORAGE SECTION, LINKAGE SECTION, CONSTANT SECTION, BASED-STORAGE SECTION, SCREEN SECTION of DATA DIVISION and PROCEDURE DIVISION.

A named-constant can only be referenced in a FILE SECTION, WORKING-STORAGE SECTION, LOCAL-STORAGE SECTION, LINKAGE SECTION, CONSTANT SECTION, BASED-STORAGE SECTION, SCREEN SECTION of DATA DIVISION and PROCEDURE DIVISION.

The data-name in the OCCURS DEPENDING ON clause must be defined in a section other than the REPORT SECTION.

If the OCCURS DEPENDING ON clause is specified in a record with an external attribute, the object must also be an item with an external attribute in the same DATA DIVISION.

If the OCCURS DEPENDING ON clause is specified in a record with a global attribute, the object must also be an item with a global attribute in the same DATA DIVISION.

The first data-name '@1@' specified in the KEY IS phrase must be either an item with an OCCURS clause or an item subordinate to an item with an OCCURS clause. The data-name is ignored.

Unless it is the first data-name specified in the KEY IS phrase, data-name '@1@' must be subordinate to an item with an OCCURS clause. The data-name is ignored.

Data-name '@1@' can only be an item with an OCCURS clause if it is the first data-name specified in a KEY IS phrase. The data-name is ignored.

The data-name '@1@' in the KEY IS phrase must not exceed 256 bytes in length. The data-name is ignored.

The length of the literal specified in the VALUE clause of the group item must not exceed the length of the item. Excess characters on the right side of the specified literal are discarded.

The length of the Boolean literal of the VALUE clause specified in the group item must be a multiple of 8. Zeros are added on the right side of the literal to make it a multiple of 8.

The length of the VALUE clause literal of the condition-name whose conditional variable is a group item cannot exceed the length of the group item. Excess characters on the right side of the specified literal are discarded.

Data-name '@2@' of the @1@ clause cannot be an item that requires a subscript.

Data-name '@2@' in the @1@ clause cannot be a variable address item.

The alphabet-name of the CODE-SET clause specified in something other than a paper tape file must be a STANDARD-1, STANDARD-2, or NATIVE specification.

The dimension number specified in the OCCURS clause cannot exceed 7.

The LINAGE clause can only be specified for a sequential file.

Data-name '@2@' in the @1@ clause is defined multiple times. The @1@ clause is ignored.

Data-name '@2@' in the @1@ clause is undefined. The @1@ clause is ignored.

The user-defined word '@2@' of the @1@ clause must be a data-name. The @1@ clause is ignored.

The data item defined in the CONSTANT SECTION must have a VALUE clause.

The EXTERNAL clause cannot be specified in file that is specified in a @1@ clause.

The EXTERNAL clause cannot be specified in a file which is specified in a MULTIPLE FILE TAPE clause.

The GLOBAL clause cannot be specified for a file that is specified in a SAME RECORD AREA clause or in its subordinate record description entry.

The PICTURE clause is missing. PICTURE 9 is assumed.

Only a USAGE clause with COMPUTATIONAL-1, COMPUTATIONAL-2, or INDEX can be specified for an elementary item without a PICTURE clause. The USAGE clause is ignored and PICTURE 9 is assumed.

The data-name with the CHARACTER TYPE clause or PRINTING POSITION clause is redefined. The print result is not guaranteed.

The CHARACTER TYPE clause can only be specified to a national, national edited, or group item.

The CHARACTER TYPE clause can be specified for an item with a REDEFINES clause only with a level-number 01 or 77 item, or in its subordinate item.

The PRINTING POSITION clause cannot be specified in a record description that includes an OCCURS DEPENDING ON clause.

The PRINTING POSITION clause can only be specified for an item with a CHARACTER TYPE clause or its subordinate item.

The PRINTING POSITION clause cannot be specified for an item with an OCCURS clause or its subordinate item.

A condition-name cannot be specified for an index data item.

The length of the redefining item cannot exceed the length of the redefined item. The redefining item overlaps no items other than ones explicitly specified.

Data-name '@2@' of the @1@ clause is not unique. The data-name is ignored.

Data-name '@2@' of the @1@ clause is undefined. The data-name is ignored.

User-defined word '@2@' in the @1@ clause must be a data-name. The user-defined word is ignored.

The BLOCK CONTAINS clause cannot be specified in a file which is referred to by a WRITE statement with an END-OF-PAGE phrase.

The record length of a file with 'F' or 'V' in the RECORDING MODE clause cannot exceed the integer specified in the BLOCK CONTAINS clause with the CHARACTERS phrase. The BLOCK CONTAINS clause is ignored.

The BLOCK CONTAINS clause with 'integer TO integer' cannot be specified in a file with a fixed length format.

The record length of the file which is sequential (organization VS or AS), relative, indexed, or of fixed length format cannot exceed 32760 bytes. A record length of 32760 bytes is assumed.

The block length of the file with a RECORDS phrase in the BLOCK CONTAINS clause or the file without the BLOCK CONTAINS clause cannot exceed 32760 bytes. A block length of 32760 bytes is assumed.

The SYNCHRONIZED clause is required for the internal Boolean item with the OCCURS DEPENDING ON clause. The SYNCHRONIZED clause is assumed.

The SYNCHRONIZED clause is required for the internal Boolean item with the indexed BY phrase in the OCCURS clause. The SYNCHRONIZED clause is assumed.

Data-name '@2@' of the DEPENDING ON phrase of the @1@ clause is defined multiple times. The DEPENDING ON phrase is ignored.

Data-name '@2@' of the DEPENDING ON phrase of the @1@ clause is undefined. The DEPENDING ON phrase is ignored.

'@2@' of the DEPENDING ON phrase of the @1@ clause must be a data-name. The DEPENDING ON phrase is ignored.

The SIGN clause with 'SEPARATE' must be specified when a data item in a file with the CODE-SET clause is a signed external decimal item. It is accepted as written.

The usage of the data item for a file with a CODE-SET clause must be DISPLAY. It is accepted as written.

A data-name must be explicitly specified for a level 01 item that is subordinate to a file with an EXTERNAL clause. The EXTERNAL clause is assumed to be valid.

A data-name must be explicitly specified for a level 01 item that is subordinate to a file with a GLOBAL clause. The GLOBAL clause is assumed to be valid.

The file name in the SAME RECORD AREA clause cannot be specified in an APPLY SAVED-AREA clause or an APPLY MULTICONVERSATION-MODE clause. It is accepted as written.

A WRITE statement with an END-OF-PAGE can refer to only one I/O area of a file. The RESERVE clause is ignored and one I/O area is assumed.

A LABEL RECORD clause with a data-name cannot be specified for a file with an EXTERNAL clause.

The @1@ clause cannot be specified for the data-item specified in the LABEL RECORD clause, or for its subordinate item.

(CONF) A RECORD CONTAINS clause containing an integer without reserved word TO cannot be specified for a presentation file.

A RECORD CONTAINS clause containing an integer without reserved word TO cannot be specified for a presentation file. The RECORD clause is ignored.

The RECORD DEPENDING ON clause cannot be specified for a file that contains a data item with a CHARACTER TYPE clause or PRINTING POSITION clause. The DEPENDING ON phrase is ignored.

Data-name with CHARACTER TYPE clause or PRINTING POSITION clause is redefined. The print result is not guaranteed.

The REDEFINES clause cannot be specified for the data-name in the APPLY SAVED-AREA clause. The REDEFINES clause is ignored.

When a file with a LINAGE clause is an external file, data-name '@1@' must be defined as an external data item.

When a file with a LINAGE clause is an external file, data-name '@1@' must be defined as an external data item. The data-name is ignored.

The object of the OCCURS DEPENDING ON phrase must be an integer.

The size of the logical page (the value of the first integer following the word 'LINAGE') must be positive. 1 is assumed.

A SYNCHRONIZED clause cannot be specified for an item that is subordinate to a group item with a VALUE clause. The SYNCHRONIZED clause is assumed to be valid.

The JUSTIFIED clause cannot be specified for an item that is subordinate to a group item with a VALUE clause. The JUSTIFIED clause is assumed to be valid.

The USAGE of an item that is subordinate to a group item with a VALUE clause must be DISPLAY. The USAGE clause is assumed valid.

The value of the integer in the FOOTING phrase must not exceed the size of the logical page. The value of the integer in the FOOTING phrase is assumed to be the same as the size of the logical page.

An @1@ item cannot be defined in the CONSTANT SECTION. It is accepted as written.

The integer (maximum number of character positions) in the RECORD clause must be equal to or greater than the record length. The RECORD clause is ignored.

The block size must be greater than or equal to the record length. The BLOCK CONTAINS clause is ignored.

'@1@' is already defined as a name with the EXTERNAL clause. The EXTERNAL clause is ignored.

The end of the area described by the THROUGH phrase data-name must be beyond the end of the area described by the RENAMES clause data-name.

The '@1@' clause cannot be specified to a sort-merge file.

The signed external decimal item with the BLANK WHEN ZERO clause is assumed to be unsigned.

Data-name '@2@' in the @1@ clause cannot be a pointer data item.

The data-name in the BASED ON clause must be a pointer data item, but not a procedure pointer data item.

The data item specified in LENGTH OF must be completed before the named-constant '@1@' is defined.

The data item specified in LENGTH OF cannot be an internal Boolean item.

The @1@ clause is specified for a data item specified in LENGTH OF. The named-constant is ignored.

The data-name of the @1@ clause must be defined in a section other than BASED-STORAGE SECTION.

Data-name '@2@' of the @1@ clause must be defined in a section other than the BASED-STORAGE SECTION. The data-name is ignored.

Data-name '@1@' in the FILE STATUS clause must be defined in the WORKING-STORAGE SECTION or LINKAGE SECTION.

Data-name '@1@' in the FILE STATUS clause must be defined in the WORKING-STORAGE SECTION, LOCAL-STORAGE SECTION or LINKAGE SECTION.

Data-name '@1@' in the FILE STATUS clause must be defined in the WORKING-STORAGE SECTION or LINKAGE SECTION. The data-name is ignored.

Data-name '@1@' in the FILE STATUS clause must be defined in the WORKING-STORAGE SECTION, LOCAL-STORAGE SECTION or LINKAGE SECTION. The data-name is ignored.

Data-name '@1@' in the FILE STATUS clause must be 2 bytes in length.

Data-name '@1@' in the FILE STATUS clause must be @2@ bytes in length. The data-name is ignored.

The data-name with the detail information in the FILE STATUS clause can only be specified in the presentation file (organization 'GS') or the print file with the FORMAT clause, sequential file (organization AS or VS), relative file, or indexed file.

The data-name or nonnumeric literal of 3 characters must be specified in the SYMBOLIC DESTINATION clause.

Nonnumeric literal @1@ of the SYMBOLIC DESTINATION clause cannot be specified.

If a qualified PAGE-COUNTER or LINE-COUNTER is specified in the SOURCE clause, the PAGE-COUNTER or LINE-COUNTER must be qualified by a unique report-name.

The identifier in the SOURCE clause is undefined.

The identifier in the SOURCE clause is not unique.

The identifier in the SOURCE clause must be a data-name, a PAGE-COUNTER, or a LINE-COUNTER.

A control data item cannot be specified in the SOURCE clause of a page heading report group or a page footing report group.

The SUM clause can only be specified in a control footing report group.

'@2@' in the @1@ clause is undefined.

'@2@' in the @1@ clause is not unique.

'@2@' in the @1@ clause must be a data-name.

Report-name '@1@' in the REPORT clause is already specified in another file. The report-name is ignored.

Report-name '@1@' in the REPORT clause is already specified in this clause. The report-name is ignored.

The report-name in the report description entry is not specified in the REPORT clause. The report description entry and the report group description entry are ignored.

Identifier '@1@' in the SUM clause must be a numeric item. The identifier is ignored.

If UPON is specified in the SUM clause, identifier '@1@' in the SUM clause must not be a data-name in the REPORT SECTION. The identifier is ignored.

If UPON is not specified in the SUM clause, data-name '@1@' in the REPORT SECTION must be a sum counter. The data-name is ignored.

If identifier '@1@' in the SUM clause is a sum counter, it must be in the same report. The identifier is ignored.

If identifier '@1@' in the SUM clause is a sum counter, it cannot be a sum counter in a control footing report group of a higher rank level. The identifier is ignored.

Data-name '@1@' in the UPON phrase must be the name of a detail report group in the same report as the control footing report group in which the SUM clause is specified. The data-name is ignored.

If the identifier in a SOURCE clause is specified in the REPORT SECTION, the identifier must be a PAGE-COUNTER, LINE-COUNTER, or a sum counter in the same report as the data-name in which the SOURCE clause is specified.

The report file must be a sequential file. This report file is ignored.

Report-name '@1@' in the REPORT clause is undefined. The report-name is ignored.

Report-name '@1@' in the REPORT clause is not unique. The report-name is ignored.

'@1@' in the REPORT clause must be a report-name. The name is ignored.

Control data-name '@1@' in the CONTROL clause is undefined. The control data-name is ignored.

Control data-name '@1@' in the CONTROL clause is not unique. The control data-name is ignored.

Control data-name '@1@' in the CONTROL clause must not be a variable length item. The control data-name is ignored.

Control data-name '@1@' in the CONTROL clause must not be an item using subscript. The control data-name is ignored.

Control data-name '@1@' in the CONTROL clause is already specified in this clause. The duplicate control data-name is ignored.

Control data-name '@1@' in the CONTROL clause must not be defined in the REPORT SECTION. The control data-name is ignored.

NEXT PAGE can only be specified in the first LINE clause of the report group. NEXT PAGE is ignored.

The LINE clause cannot be specified in a subordinate item of a group item with a LINE clause. Compilation continues.

If a relative value LINE clause is already specified for a report group, an absolute value LINE clause cannot be specified for that group.

The integers of absolute value LINE clause must be specified in ascending order.

Control data-name '@1@' in the CONTROL clause must not be a procedure pointer data-item.

If a PAGE clause is not specified in a report description entry, an absolute value LINE clause cannot be specified.

If a LINE clause is specified in the report heading report group, page heading report group, or page footing report group, NEXT PAGE cannot be specified.

The first LINE clause in the page footing report group must be an absolute value LINE clause.

A report with a CODE clause and a report without a CODE clause cannot be specified together for the same report file. Compilation continues.

If a PAGE clause is not specified in a report description entry, a NEXT GROUP clause must be specified using a relative value format.

If a NEXT GROUP clause is specified in the page footing report group, NEXT PAGE cannot be specified.

The NEXT GROUP clause cannot be specified in a report footing report group or a page heading report group.

A report group of particular type (RH, PH, CH FINAL, CF FINAL, RF, PF) can only be specified once in the same report. Compilation continues.

If a PAGE clause is not specified in the report description entry, the page heading report group and page footing report group cannot be specified. Compilation continues.

Control data-name '@1@' of the TYPE clause is undefined.

Control data-name '@1@' of the TYPE clause is not unique.

'@1@' specified in the TYPE clause must be a data-name.

If FINAL is not specified in the CONTROL clause, FINAL cannot be specified in the TYPE clause.

The positions of printable items have been specified so that they overlap. Compilation continues.

The GROUP INDICATE clause can only be specified in a detail report group.

Data-name '@1@' must be subscripted.

Data-name '@2@' is a subscripted item that cannot be used as a subscript or reference modifier for the @1@ clause. Subscript or reference modifier 1 is assumed.

'@1@' specified in the TYPE clause must be a control data-name.

A control heading report group or a control footing report group can only be specified once in the same control level.

'@1@' in the CONTROL clause must be a data-name. The name is ignored.

The integer in the @1@ clause cannot exceed the upper limit provided by the presentation rule. Compilation continues.

The integer in the @1@ clause cannot be less than the lower limit provided by the presentation rule. Compilation continues.

The word '@2@' in the @1@ clause is invalid. It is ignored, and the compiler skips to the next valid identifier, clause, paragraph, section or division.

Invalid word '@1@' appeared in an identifier of the SOURCE clause. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

Invalid word '@1@' appeared in an identifier of the SUM clause. It is ignored, and the compiler skips to the next valid identifier, clause, paragraph, section or division.

A subscript cannot be specified in identifier '@1@' in the SUM clause. The subscript is ignored.

Invalid word '@2@' appeared in the subscript of the @1@ clause. Subscript 1 is assumed.

A right parenthesis is missing in the subscript or reference modifier. A right parenthesis is assumed.

Invalid word '@1@' appeared in the reference modifier of the SOURCE clause. Reference modifier 1 is assumed.

The reference modifier in the SOURCE clause must have a colon. A colon is assumed.

'@2@' specified as a subscript in the @1@ clause must be a unique data-name or index-name. Subscript 1 is assumed.

'@1@' specified as a reference modifier in the SOURCE clause must be a unique data-name. Reference modifier 1 is assumed.

A RESET clause cannot be specified in a report without a CONTROL clause.

If FINAL is specified in the RESET clause, FINAL must also be specified in the CONTROL clause.

Data-name '@1@' of the RESET clause must be a control data-name of an equal or higher level control to this clause in the control hierarchy.

A TYPE clause is not specified in the 01 level item of the report group description entry. This report group description entry is ignored.

The NEXT GROUP clause cannot be specified in a report group description entry without a LINE NUMBER clause. Compilation continues.

The USAGE clause specified in the report group description entry must be specified in a group item with a printable item. Compilation continues.

The COLUMN clause and the PRINTING POSITION clause cannot both be specified the same report group. Compilation continues.

The elementary item of a report group description entry must be specified with either the SOURCE clause, the SUM clause, or the VALUE clause. Compilation continues.

No valid word is specified in a subscript or reference modifier in the identifier of the @1@ clause. Subscript or reference modifier 1 is assumed.

If a subscript is specified in the identifier of the @1@ clause, an integer must be specified after '+' or '-' following the index-name. 1 is assumed for the integer.

The elementary item requires a PICTURE clause. PICTURE X is assumed.

The @1@ clause in the REPORT SECTION cannot be specified in a group item or an 01 level elementary item.

The PICTURE clause in the REPORT SECTION cannot be specified in a 01 level item. Compilation continues.

The @1@ clause in the REPORT SECTION must be specified in a printable item. Compilation continues.

If the USAGE clause in the REPORT SECTION is specified for an elementary item, it must be printable item. Compilation continues.

The COLUMN NUMBER clause can only be specified in an entry with a LINE NUMBER or an entry that is subordinate to an entry with a LINE NUMBER. Compilation continues.

A sum counter cannot be specified in a subscript or reference modifier in a SUM clause or a SOURCE clause. Compilation continues.

The SAME RECORD AREA clause cannot be specified for a report file. Compilation continues.

If a RECORD clause is specified for a report file, VARYING cannot be specified.

RECORD CONTAINS 0 CHARACTERS cannot be specified for a report file.

The report writer logical record with a CHARACTER TYPE clause or PRINTING POSITION clause is too long. @1@ is used for the record length.

The value of the COLUMN clause is too large. The length of the report writer logical record is expanded to include the specified item at the specified column.

The report writer logical record is too long. RECORD CONTAINS @1@ is assumed.

The integer in the NEXT GROUP clause cannot exceed the documented upper limit.

The integer in the NEXT GROUP clause cannot be less than the documented lower limit.

The compiler has encountered a word '@1@' where a statement is expected.

'@2@' in the @1@ statement must be @3@.

'@2@' in the @1@ statement must be @3@. '@2@' is ignored.

User word '@1@' is undefined.

User word '@1@' is defined multiple times.

'@2@' must be specified in the @1@ statement. '@2@' is assumed.

A statement must be specified in a conditional statement or an in-line PERFORM statement. It is accepted as written.

The IF DB-EXCEPTION statement cannot precede a data base operation statement or an IF DB-EXCEPTION statement.

NEXT SENTENCE cannot be specified in an IF or SEARCH statement with an explicit scope terminator. It is accepted as written.

Conditional statement '@1@' is specified where an imperative statement should be specified. The @1@ statement is assumed to be valid.

'@1@' does not correspond. '@1@' is ignored.

'@2@' in the @1@ statement must be a mnemonic-name or a function-name. SYSIN or SYSOUT is assumed.

INPUT, OUTPUT, I-O, or EXTEND is missing from the OPEN statement. The compiler skips to the next INPUT, OUTPUT, I-O, or EXTEND.

Invalid word '@1@' is specified where a file other than a sort-merge file must be specified. Word '@1@' is ignored.

The '@3@' option cannot be specified in the '@2@' file with an '@1@'. The option is ignored.

NO REWIND cannot be specified in the '@2@' file with an '@1@'. NO REWIND is ignored.

'@2@' in the @1@ statement must be a file other than a sort-merge file.

An invalid word is specified where a procedure-name must be specified in the @1@ statement. The invalid word is ignored.

'@1@' in the USING phrase must be an identifier, a procedure-name, or a file-name.

'@2@' after '@1@' must be a procedure-name.

'@2@' is invalid in a @1@ statement.

In the PERFORM statement, the TEST BEFORE or TEST AFTER phrase is incomplete. A 'TEST BEFORE' phrase is assumed.

No more than six AFTER phrases should occur in a VARYING phrase of a PERFORM statement. It is accepted as written.

'@2@' is specified where '@1@' must be specified.

Invalid operand '@2@' with '@1@' is specified.

The operand in the @1@ phrase is missing or invalid. 1 is assumed as the operand.

The identifier in the SEARCH statement cannot be subscripted or reference modified. It is ignored, and the compiler skips to the next AT END or WHEN clause.

A period, ELSE phrase, or WHEN phrase must follow NEXT SENTENCE. It is accepted as written.

An invalid arithmetic expression is specified in the SEARCH ALL statement.

The relational operator is missing.

The @1@ phrase cannot be specified. The phrase is ignored.

'@1@' is invalid as a program-name or entry-name.

A figurative constant ZERO(S, ES) cannot be specified in a selection subject. ZERO(S, ES) is accepted.

'@2@' cannot be specified in a @1@ statement.

Index-name '@1@' cannot be specified in a selection subject or selection object.

The number of selection objects must equal the number of selection subjects. The compiler assumes the appropriate number of ANY words, and compilation continues.

The number of selection objects is greater than the number of selection subjects. Their numbers must be equal. Excess selection objects are ignored.

The paragraph containing the EXIT statement can only consist of the procedure-name and the EXIT statement itself. The EXIT statement is considered to be a CONTINUE statement in this context.

The same category cannot be specified in the REPLACING phrase of the INITIALIZE statement.

A user-defined word must follow IN or OF. The IN or OF is ignored.

An invalid word is specified in the arithmetic expression of the @1@ statement.

The ALL literal cannot be specified in a @1@ statement. The word ALL is ignored.

The format of the specification '@1@' is invalid.

Only the optional word '@1@' is specified. '@1@' is ignored.

'@2@' in the @1@ statement must be a report-name or a data-name.

The @1@ statement must contain key word '@2@'.

An index-name, index data item, integer item, or positive integer must follow TO in the SET statement.

Integer item or integer must follow 'UP BY' or 'DOWN BY' in SET statement.

A word which indicates a category must follow REPLACING in the INITIALIZE statement. The code is ignored until the next statement or procedure-name.

An identifier or literal must follow BY in the INITIALIZE statement. The code is ignored, and the compiler skips to the next word representing a category or statement.

The USE statement can only be specified in DECLARATIVES.

The format of the @1@ statement is incomplete.

The @1@ statement can only have one @2@ phrase. The first @2@ phrase is used and the other @2@ phrases are ignored.

The section-name must be followed by a USE statement in DECLARATIVES. It is accepted as written.

The KEY phrase of the READ or START statement contains no valid operand. The KEY phrase is ignored.

'@1@' must be a record-name in a sort-merge file.

'@2@' in the @1@ statement must be a sort-merge file name.

An invalid operand is specified in the arithmetic expression. The arithmetic expression is ignored.

The RETURN statement must have an AT END phrase. The AT END CONTINUE phrase is assumed.

The condition in the @1@ statement is invalid.

The SUPPRESS statement can only be specified in the USE BEFORE REPORTING procedure.

The subscript must be an arithmetic expression or an index-name with an optional +integer or -integer. 1 is assumed for the subscript.

@1@ must be subscripted.

The right parenthesis of the subscript or reference modification is not specified. A right parenthesis is assumed.

The SORT or MERGE statement must have an ASCENDING or DESCENDING phrase. An ASCENDING phrase is assumed.

The number of key data-names in the SORT or MERGE statement cannot exceed 64. Excess data-names are ignored.

The number of file-names specified in the USING phrase of the SORT or MERGE statement cannot exceed 16. Excess file-names are ignored.

The @1@ statement cannot be specified in DECLARATIVES. It is accepted as written.

The format of the high-order-end-character-position of the reference modification is invalid. 1, the first character, is used.

The length specification in the reference modification is invalid. The reference modifier without a length specification is assumed.

The @1@ statement cannot be specified in the USE BEFORE REPORTING procedure.

There is no valid report description entry in the program containing the @1@ statement.

The @1@ statement cannot be specified in a program contained directly or indirectly within another program.

The '@1@' phrase cannot appear before a GIVING phrase in an ADD, DIVIDE, MULTIPLY, or SUBTRACT statement.

'@2@' in the @1@ statement must be a record-name of a file that is not a sort-merge file.

'@1@' in the WRITE statement must follow AFTER or BEFORE. AFTER is assumed.

Invalid word '@1@' is specified in a @2@ phrase. 1 is assumed.

LINE(S) can only be specified when the @1@ phrase has an integer or an identifier. LINE(S) is ignored.

The WHEN phrase must precede the WHEN OTHER phrase in the EVALUATE statement.

The sign condition cannot be specified for a selection subject or a selection object of an EVALUATE statement.

The combination of relational operators in the condition is invalid.

NOT cannot be repeated as it is in this condition.

The operand of the condition is invalid.

@2@ is specified instead of @1@. 1 is assumed.

The right parenthesis corresponding to the left parenthesis is missing. A right parenthesis is assumed.

The @1@ statement cannot be specified in a declarative procedure with a global specified.

'@1@' in the USING phrase must be a level 01 or 77 item defined in the LINKAGE SECTION of this program.

Condition-name '@1@' specified in the SEARCH ALL statement must be defined as having a single value.

An integer must be specified after '+' or '-' following the index-name. The subscript of that dimension is assumed to be 1.

A @2@ statement with a @1@ requiring execution at the same time can only be specified once.

Only one @1@ statement can be specified in the outermost program.

The USE DEBUGGING statement must be specified first in DECLARATIVES.

Data-name '@1@' specified in the KEY phrase must be a data-name of the sort-merge file specified for this SORT or MERGE statement.

Mnemonic-name '@1@' specified for the ASCENDING phrase in the SORT or MERGE statement must correspond to function-name BUSHU, SOKAKU, ON-YOMI, KUN-YOMI, BUSHOU, HUASHU, DUYIN, BUSU, HOEK or JAMO.

The mnemonic-name corresponding to the Japanese, Chinese, or Korean function-name must exclusively be specified in the ASCENDING phrase of a SORT or MERGE statement.

The AFTER phrase cannot be specified for an in-line PERFORM statement.

The left parenthesis corresponding to the right parenthesis is missing. The extra right parenthesis is ignored.

The invalid word THEN is specified. THEN is ignored.

The SQL statement is invalid. @1@.

Cursor name '@1@' is not defined.

The invalid word '@1@' follows a THROUGH (THRU) phrase in a selection object of an EVALUATE statement. The THROUGH (THRU) phrase is ignored.

An END-PERFORM phrase must be specified in the in-line PERFORM statement. END-PERFORM is assumed.

The word SENTENCE is not specified in NEXT SENTENCE. The word SENTENCE is assumed.

The word '@2@' is not specified in '@1@'. The word '@2@' is assumed.

The @1@ statement cannot be used when a SUBSCHEMA-NAME paragraph is not specified.

'@2@' cannot be specified in a @1@ statement.

The numeric literal of the EXAMINE statement must be unsigned. The sign is ignored.

(CONF) The explicit scope terminator '@1@' is assumed to correspond with the previous @2@ statement.

The numeric literal and the sign are separated. The sign and the numeric literal are assumed to be concatenated.

File '@1@' in the USE LABEL statement must be a sequential, direct organization, or relative organization file. The '@1@' file is ignored.

A data-name must be specified by the LABEL RECORD clause for file '@1@' specified in the USE LABEL statement. '@1@' is ignored.

REEL and UNIT cannot be specified for file '@1@' in the random access mode.

The USE LABEL statement with BEFORE is not supported.

'@1@' in the USE BEFORE REPORTING statement must be a report group name.

The syntax of the WHENEVER statement is invalid.

The procedure-name '@1@' in the effective WHENEVER statement is undefined or multi-defined. The GO TO procedure-name is replaced by CONTINUE.

The identifier '@1@' in the effective WHENEVER statement must be a procedure-name. The GO TO procedure-name is replaced by CONTINUE.

'@1@' must be 136 bytes and defined in the WORKING-STORAGE SECTION. The GIVING phrase is ignored.

'@1@' must be 136 bytes and defined in the WORKING-STORAGE SECTION or LOCAL-STORAGE SECTION. The GIVING phrase is ignored.

'@1@' must be defined in the WORKING-STORAGE SECTION or the LINKAGE SECTION. '@1@' is ignored.

'@1@' must be defined in the WORKING-STORAGE SECTION, the LOCAL-STORAGE SECTION or the LINKAGE SECTION. '@1@' is ignored.

The @1@ statement can only be coded once in a program.

':' must be specified in the reference modifier. ':' is assumed.

The @1@ phrase contains no valid operand.

Invalid word @2@ appears in the @1@ statement.

A parenthesis cannot be specified in an abbreviated combined relation condition. The parenthesis is assumed to be valid.

The cursor name '@1@' is already defined.

More than one file-name must be specified in the USING phrase of the MERGE statement. Compilation continues.

'@1@' in the REPORT SECTION cannot be referred in the PROCEDURE DIVISION.

A non-operative statement exists after the @1@ statement. The syntax of the statement is assumed to be valid, but the statement is not executed.

'@1@' must be an identifier or a non-zero integer. It is accepted as written.

The pointer qualifier is invalid.

'@1@' qualified by a pointer must be a data-name or a condition-name. The pointer qualification is ignored.

An EXIT PERFORM statement with a TEST phrase cannot be specified in an in-line PERFORM statement without a testing mechanism. The TEST phrase is ignored.

The EXIT PERFORM statement must be specified inside of an in-line PERFORM statement.

The argument in @1@ is not specified.

The argument in @1@ must be @2@.

The right parenthesis of the function is not specified. A right parenthesis is assumed.

The DEBUGGING SECTION is assumed to be a comment.

The VALUE clause cannot be specified for an item specified in an EXTERNAL clause or for its subordinate item. The VALUE clause is ignored.

The VALUE clause cannot be specified for an item specified in a REDEFINES clause or for its subordinate item. The VALUE clause is ignored.

The VALUE clause cannot be specified for an item specified in the APPLY SAVED-AREA clause or for its subordinate item. The VALUE clause is ignored.

'@1@' must be qualified by an identifier.

A 'REVERSED ORDER' phrase cannot be specified in a START statement with ascending order.

The paragraph including the GO TO statement without a procedure-name must contain only a paragraph-name and a single GO TO statement. The GO TO statement is ignored.

Data-name '@2@' in the @1@ statement cannot be qualified by a pointer. The pointer qualification is ignored.

(OBS) The @1@ statement is an obsolete element in @2@ COBOL.

(OBS) The @1@ phrase is an obsolete element in @2@ COBOL.

(OBS) The GO TO statement without a procedure-name is an obsolete element in ANSI85 COBOL.

(OBS) The STOP statement with a literal is an obsolete element in ANSI85 COBOL.

(OBS) @1@ is an obsolete feature in @2@ COBOL.

'@2@' in special register '@1@' must be an identifier.

The identifier in special register '@1@' must be a level 01 or 77 item defined in the LINKAGE SECTION.

ON or OFF must follow TO in the SET statement.

TRUE must follow TO in the SET statement.

A pointer data item, NULL(S), or ADDRESS OF special register must follow TO in the SET statement.

The LENGTH OF special register cannot be specified in the receiving item of a @1@ statement.

'@1@' must be a level 01 or 77 item.

SQLERRD must be an 02 level item immediately subordinate to an 01 level SQLINFOA or be an item immediately subordinate to an 01 level SQLCA, and it must be specified with OCCURS 6 TIMES. Also, a DEPENDING ON phrase, a KEY IS phrase, and an INDEXED BY phrase cannot be specified for an OCCURS clause.

The host variable cannot be a variable address item.

The host variable cannot be subordinate to a data item with a @1@ clause.

A host variable with an OCCURS clause must be either an elementary item with a level number other than 49, or a group item that corresponds to a variable length column.

An OCCURS clause with a DEPENDING ON phrase, a KEY IS phrase, and an INDEXED BY phrase cannot be specified for a host variable.

The host variable cannot be a strongly typed item.

The global name of the host variable must be unique with no qualifiers in its scope if it is declared as a group item or subordinate item. All names in this group item are invalid as a host variable name.

The embedded @1@ statement must end with END-EXEC. All embedded @1@ statements following the EXEC @1@ are ignored.

The SQLCODE or SQLSTATE is undefined or defined multiple times.

Invalid characters are specified in the SQL statement. This SQL statement is ignored.

The number of host variables that can be referenced has been exceeded. Compilation is terminated.

@1@STATE is not specified or it is not unique.

Special register @1@ can only be specified as a sending item in a MOVE statement.

In this system, '@1@' cannot be used.

'@1@' is assumed to be a comment in this system.

The number of the argument in '@1@' must be greater than 1.

'@1@' cannot be specified in a receiving item.

The subscript 'ALL' cannot be specified in '@1@'. The subscript is assumed to be 1.

The '@2@' phrase in the '@1@' statement is invalid.

'@1@' is assumed to be a comment in this system.

Mnemonic-name '@1@' is assumed to be a comment in this system.

'@1@' is a function that is specific to the MSP or XSP system.

When a mnemonic-name in the UPON clause is related to function-name ARGUMENT-NUMBER, ENVIRONMENT-NAME, or ENVIRONMENT-VALUE, only one identifier or literal can be specified for the DISPLAY statement.

'@1@' is a function that is specific to the MSP or XSP system.

The host variable of a binary item must be 4 or 9 digits.

The host variable of a binary item must be @1@ digits.

The data-name in @1@ clause must be defined in the WORKING-STORAGE SECTION or LINKAGE SECTION.

The data-name in @1@ clause must be defined in the WORKING-STORAGE SECTION, LOCAL-STORAGE SECTION or LINKAGE SECTION.

The data-name in the @1@ clause must be an alphanumeric or group item. The group item should not be one that includes an object reference item.

The data-name in the @1@ clause must be @2@ bytes in length.

The data-name in the MESSAGE CODE clause must be an alphanumeric item or an unsigned external decimal item that is an integer.

The name of the PRINTING POSITION clause must be a unique positioning-unit-name.

The data-name in the @1@ clause must not exceed @2@ bytes in length.

Data-name '@2@' in the @1@ clause of the RDB indexed file must be specified for an alphanumeric, national, internal decimal, binary, or group item. An alphanumeric item is assumed.

A presentation file (organization 'GS') with an APPLY MULTICONVERSATION-MODE clause must also specify an APPLY SAVED-AREA clause for that presentation file.

The VALUE clause cannot be specified for a subordinate item of a group item with a VALUE clause. The VALUE clause is ignored.

A VALUE clause cannot be specified for a variable-address item. The VALUE clause is ignored.

If the presentation file (organization 'GS') is not defined, a file-name must be specified in the @1@ clause.

@1@ must be an alphanumeric item.

The @1@ clause cannot be specified in a presentation file (organization 'GS').

Data-name '@1@' in the KEY IS phrase must be a binary, internal decimal, external decimal, numeric edited, alphabetic, alphanumeric, alphanumeric edited, national, or national edited item.

A RECORDING MODE clause cannot be specified for a sequential (organization 'VS' or 'AS'), relative, indexed, presentation, or print file with a FORMAT clause. The RECORDING MODE clause is ignored.

The record length of the presentation file, chart file, or print file with a FORMAT clause cannot exceed 32767 bytes. A record length of 32767 bytes is assumed.

The data-name in the '@1@' clause must be an unsigned external decimal item that is an integer without the symbol 'P'.

Data-name '@1@' in the KEY IS phrase cannot be a variable-length item.

The mnemonic-name in the CHARACTER TYPE clause is undefined, defined multiple times, or related to an invalid function-name.

The mnemonic-name in the CHARACTER TYPE clause is related to a function-name that is not supported in the report writer module.

The FORMATTED RECORD clause can only be specified for a presentation file, chart file, or print file with a FORMAT clause.

A CONTROL RECORD clause can only be specified for a presentation file or a print file with a FORMAT clause.

Only one data-name can be specified in the RECORD KEY clause of an indexed organization file. The first data-name is used.

'@1@' must be a unique symbolic constant.

A pointer data item can only be defined in the BASED-STORAGE SECTION, WORKING-STORAGE SECTION, LOCAL-STORAGE SECTION, CONSTANT SECTION, or LINKAGE SECTION.

The PRINTING POSITION clause cannot be specified for a pointer data item.

A numeric literal cannot be specified in the VALUE clause of an alphanumeric, alphanumeric edited, or group item. A nonnumeric literal of the same length is assumed to be specified.

A numeric literal cannot be specified in a VALUE clause of a condition-name for a conditional variable of an alphanumeric, alphanumeric edited, or group item. A nonnumeric literal of the same length is assumed to be specified.

A RECORD clause with a VARYING phrase cannot be specified for a relative organization file.

The figurative constant NULL cannot be specified in a VALUE clause except for a pointer data item.

The figurative constant ZERO or NULL must be specified in the VALUE clause of a pointer data item.

The figurative constant ZERO or NULL must be specified in the VALUE clause of the condition-name for the conditional variable of the pointer data item.

File '@1@' in the APPLY WRITE-ONLY clause must be a sequential file with a variable length format.

The data-name in the @1@ clause must be defined in the WORKING-STORAGE SECTION, LOCAL-STORAGE, LINKAGE SECTION, or CONSTANT SECTION.

COMPUTATIONAL-4 must be specified for the numeric item.

The item redefined by the REDEFINES clause is a variable-length item. The REDEFINES clause is assumed to be valid.

The redefining item contains a variable occurrence data item. The REDEFINES clause is assumed to be valid.

A SIGN clause is specified for an external floating-point item. The SIGN clause is assumed to be a comment.

The host variable of a binary item cannot contain the symbols P and V, and must be 4 or 9 digits.

The host variable of a binary item cannot contain the symbols P and V, and must be @1@ digits.

The host variable defined as an alphanumeric item must not exceed @1@ bytes in length.

The number of characters for the host variable defined as a national item cannot exceed @1@.

The host variable of an internal decimal item cannot contain the symbol P.

The host variable must be a binary, external decimal, alphanumeric, national, internal float, internal decimal, or fixed length group item.

Items subordinate to a host variable of variable-length string type must be a combination of a signed binary item and either an alphanumeric item or a national item.

A binary item that is subordinate to a host variable of variable-length string type cannot contain the symbols P and V, and must be 4 or 9 digits.

An alphanumeric item that is subordinate to a host variable of variable-length string type cannot exceed @1@ bytes in length.

The number of characters for a national item that is subordinate to a host variable of variable-length string type cannot exceed @1@ characters.

The host variable of a binary item must be 4 or 9 digits. It is accepted as written.

The host variable of a binary item must be @1@ digits. It is accepted as written.

When the SIGN clause is specified for a host variable that is a signed external decimal item, LEADING SEPARATE or TRAILING must be specified.

@1@ must be an alphanumeric item of 5 characters.

The SQLCODE must be a signed binary item of 9 digits and cannot contain symbols P or V. It is accepted as written.

@1@ must be a signed binary item of 9 digits and cannot contain the symbols P or V.

If a redefined item is a variable-length item, or if a redefining item contains a variable occurrence data item, the offset of this item cannot be determined.

A sort-merge file can only specify a file-identifier in an ASSIGN clause. It is accepted as written.

The FORMATTED RECORD clause cannot be specified for a print file with a FORMAT clause.

The host variable of a binary, external decimal, or internal decimal item must contain the symbol S.

The @1@ clause cannot be specified for a host variable.

'0' cannot be specified after '+' or '-' following an index-name. It is accepted as written.

The '@1@' clause cannot be specified for the record description entry of a sort-merge file.

'RECORD CONTAINS 0' cannot be specified in a sort-merge file description entry.

Data-name '@1@' in the APPLY SAVED-AREA clause cannot be an external data item. The data-name is ignored.

The SUM clause can only be specified in an external decimal item, alphanumeric item, numeric edited item, alphanumeric edited item, and external floating-point item.

(CONF) The record length is assumed to be the value of the RECORD CONTAINS clause.

(CONF) A relational operator appears just after the word 'NOT' in the abbreviated combined relation condition. The word 'NOT' assumed to be part of the relational operator.

A relational operator is not specified or is missing.

The @1@ phrase of the START statement can only be specified for an indexed organization file.

When a file that is specified as a RELATIVE KEY clause is external, the data item of the RELATIVE KEY clause must be external.

A 'CHARACTER TYPE' clause with an OR phrase cannot be specified for an elementary item.

Printing-mode-name '@1@' specified in the CHARACTER TYPE clause is undefined or defined multiple times.

A printing-mode-name with a 'FOR ALL' can only be specified for a group, alphabetic, alphanumeric, alphanumeric edited, external decimal, external boolean, external floating point, numeric edited, national, or national edited item.

A printing-mode-name with a 'FOR MOCS' can only be specified for a group, national, or national edited item.

A printing-mode-name with 'FOR SOCS' can only be specified for a group, alphabetic, alphanumeric, alphanumeric edited, external decimal, external boolean, external floating point, or numeric edited item.

A printing-mode-name with 'FOR ALL' cannot be specified for a CHARACTER TYPE clause with an OR phrase.

When two or more printing-mode-names are specified, all FOR phrases for the printing-mode-names must be the same.

The FOR phrases for printing-mode-names after an OR phrase must be different from those before the OR phrase.

A 'CHARACTER TYPE' clause with MODE-1, MODE-2, MODE-3, or a mnemonic-name cannot be specified for a record description entry containing an item that is specified for a 'CHARACTER TYPE' clause with a printing-mode-name.

The data-name of the '@2@' phrase in the '@1@' clause must be an integer item defined in the WORKING-STORAGE, FILE, CONSTANT, or LINKAGE SECTION.

The data-name of the '@2@' phrase in the '@1@' clause must be an integer item defined in the WORKING-STORAGE, LOCAL-STORAGE, FILE, CONSTANT, or LINKAGE SECTION.

If a CHARACTER TYPE clause with a DEPENDING ON phrase is specified in a record with an external attribute, then the data-name of the 'DEPENDING ON' phrase must also be an item with an external attribute in the same DATA DIVISION.

If a CHARACTER TYPE clause with a DEPENDING ON phrase is specified in a record with a global attribute, then the data-name of the DEPENDING ON phrase must also be an item with a global attribute in the same DATA DIVISION.

The data-name in the CURSOR clause must be defined in the WORKING-STORAGE SECTION, it must be 4 or 6 bytes in length, and its usage must be DISPLAY.

The data-name in the CRT STATUS clause must be defined in the WORKING-STORAGE SECTION, and it must be 3 bytes in length.

The JUSTIFIED clause cannot be specified in a screen description entry with a FULL clause. The JUSTIFIED clause is ignored.

The @1@ clause cannot be specified for an item that has a PICTURE clause with a @2@ phrase. The @1@ clause is ignored.

The @1@ clause cannot be specified for an item that has a PICTURE clause with a @2@ phrase.

A BELL, BLANK, COLUMN, LINE, PICTURE or VALUE clause must be specified for the elementary item in the SCREEN SECTION.

The @1@ clause cannot be specified for the group item in the SCREEN SECTION.

'@2@' which is specified in @1@ must be an identifier or a literal.

'@2@' that is specified in @1@ must be an identifier.

'@2@' that is specified in @1@ must be an identifier or an integer.

Invalid word '@1@' is found. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

The right parenthesis of the subscript or reference modification is not specified. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

An integer must be specified after '+' or '-' following the index-name. It is ignored, and the compiler skips to the next valid clause, paragraph, section, or division.

The subscript must be an arithmetic expression, an index-name with optional +integer or -integer, or 'ALL'. It is ignored, and the compiler skips to the next valid clause, paragraph, section, or division.

The name '@1@' is not unique. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

The character that constructs the file-identifier is invalid, or the file-identifier name exceeds 8 characters. The name of file-identifier is assumed to be valid. If the name exceeds 8 characters, the first 8 characters are assumed to be valid.

The file-identifier is invalid.

Identifier '@2@' that is specified in @1@ must be defined in the FILE, WORKING-STORAGE, LINKAGE, BASED-STORAGE or CONSTANT SECTION. Ignored until the next valid clause, paragraph, section or division.

Identifier '@2@' that is specified in @1@ must be defined in the FILE, WORKING-STORAGE, LOCAL-STORAGE, LINKAGE, BASED-STORAGE or CONSTANT SECTION. Ignored until the next valid clause, paragraph, section or division.

Identifier '@2@' that is specified in @1@ must be defined in the FILE, WORKING-STORAGE, LINKAGE or BASED-STORAGE SECTION. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

Identifier '@2@' that is specified in @1@ must be defined in the FILE, WORKING-STORAGE, LOCAL-STORAGE, LINKAGE or BASED-STORAGE SECTION. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

The right parenthesis corresponding to the left parenthesis is not specified. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

The '@1@' clause cannot be specified in a line sequential file.

The data-name of the ASSIGN clause in file-name '@1@' must be an alphanumeric data-item that is less than 256 characters and defined in the WORKING-STORAGE SECTION or LINKAGE SECTION.

The data-name of the ASSIGN clause in file-name '@1@' must be an alphanumeric data-item that is less than 256 characters and defined in the WORKING-STORAGE SECTION, LOCAL-STORAGE SECTION or LINKAGE SECTION.

The format of the reference modifier is invalid. It is ignored, and the compiler skips to the next valid clause, paragraph, section or division.

The WITH phrase of the @1@ statement must be C, PASCAL, or STDCALL. The WITH phrase is ignored.

The WITH phrase of the PROCEDURE DIVISION must be C, PASCAL, or STDCALL. The WITH phrase is ignored.

The WITH phrase of the ENTRY statement must be the same as the WITH phrase of the PROCEDURE DIVISION. It is accepted as written.

The AT phrase and the LINE or COLUMN phrase are mutually exclusive in the @1@ statement. The @2@ phrase is ignored.

@2@ can only be specified once in the WITH phrase of the @1@ statement. The WITH phrase is ignored.

@2@ and @3@ are mutually exclusive in the WITH phrase of the @1@ statement. The WITH phrase is ignored.

@2@ cannot be specified in the WITH phrase of the @1@ statement. @2@ is ignored.

@2@ is invalid in the WITH clause of the @1@ statement.

The @2@ phrase must be CRT in the @1@ statement with an AT, LINE, COLUMN, MODE, or WITH phrase.

The data item in the SCREEN SECTION must be referenced as a data name.

SQLSTATE or SQLCODE can define only a level 01 item or level 77 item, or the item subordinate to a level 01 SQLCA.

Only one of the following can be defined: either an SQLERRD subordinate to an SQLINFOA, or an SQLERRD subordinate to an SQLCA.

'@1@' must be an item that does not specify the OCCURS clause immediately subordinate to a level 01 SQLCA.

'@1@' cannot be used by a PROGRAM DEFINITION that contains the RECURSIVE attribute.

COBOL words are limited to 30 characters each. The first 30 characters are used as the COBOL word.

A 'FROM', 'TO', or 'USING' phrase must be specified in the PICTURE clause of the screen description entry.

The @1@ clause cannot be specified for the numeric item or numeric edited item in the SCREEN SECTION.

The data-name in the FORMAT clause specified for the presentation file of destination XAP or PRT must be 30 bytes or less in length.

STRING statement or UNSTRING statement with CSV-FORMAT/TSV-FORMAT cannot be used when the DECIMAL-POINT IS COMMA clause is specified in the SPECIAL-NAMES paragraph.

Figurative constants other than SPACE cannot be specified in a STRING statement with CSV-FORMAT or TSV-FORMAT.

The length of the national item or national edited item defined in Encoding as UTF32 must be less than 536870911 characters. It is taken as 536870911 characters.

Invalid characters are specified in @1@. This statement is ignored.

The value of the subscript of @2@th dimension for @1@ must be positive. 1 is used for the subscript value.

The value of the subscript of the @2@th dimension for @1@ must not exceed @3@. 1 is used for the subscript value.

The number of subscripts for @1@ must be @2@. Extra high-order-end subscripts are ignored.

The number of subscripts for @1@ must be @2@. The value of each higher dimension subscript is replaced with 1.

Index-name @3@ of the @2@th dimension for @1@ must be specified using the INDEXED BY phrase of that table. It is assumed that the index-name is an index for that table.

The usage of the reference modified data item @1@ must be 'DISPLAY'. Usage 'DISPLAY' is assumed.

The length of the reference modifier for @1@ must be greater than zero. A length of 1 is assumed.

The leftmost-character-position of the reference modifier for @1@ must be greater than zero. The leftmost-character-position is assumed to be 1.

The length of the reference modifier for @1@ cannot exceed @2@. A length of 1 is assumed.

The leftmost-character-position of the reference modifier for @1@ cannot exceed @2@. The leftmost-character-position is assumed to be 1.

The sum of the leftmost-character-position and the length of the reference modifier for @1@ cannot exceed @2@. The leftmost-character-position and the length are both assumed to be 1.

The value of the divisor is zero, where zero is a numeric literal with a value of 0, a figurative constant 'ZERO', or the result of an operation with no significant digits. A value consisting of all 9's is moved to the receiving item, with the number of digits being determined from the PICTURE clause of the receiving item. When the receiving item is an arithmetic expression, the number of digits is 30.

There are no significant digits in the intermediate result of the operation. The result is assumed to be zero.

Computing the zero power of zero occurred, where zero is a numeric literal with value 0, figurative constant 'ZERO', or a result of an operation with no significant digits. The result is assumed to be zero.

(CONF) During a move between a nonnumeric operand and a numeric operand, the numeric operand has 'P' to left of the decimal point. The numeric operand was moved, assuming zero at the position of 'P'.

(CONF) A Boolean item or Boolean literal is moved to an alphanumeric item. An elementary move between two alphanumeric items is assumed.

(CONF) The ALL literal is moved to a numeric item or numeric edited item. The literal is repeated, character by character, until its size is equal to the size of the receiving operand.

(CONF) The group item including the item with the OCCURS DEPENDING ON clause and its object item is specified in the receiving operand. The maximum length of the receiving item is assumed.

A nonnumeric literal moved to a numeric item can consist only of numeric characters.

The value of the numeric literal that is moved to the binary item cannot exceed the maximum value that can be held in the receiving item.

Non-integer item @1@ cannot be moved to alphanumeric item @2@. After moving the sending operand to an unsigned external decimal item with the same digits as the sending operand, the alphanumeric item redefining that external decimal item is moved to the receiving alphanumeric item.

@1@ cannot be moved to @2@.

The intermediate result cannot contain more than 30 digits. The intermediate result is assumed to have 30 digits.

The intermediate result cannot contain more than @1@ digits. The intermediate result is assumed to have @1@ digits.

A Boolean expression cannot be specified in a conditional expression.

Identifier @1@ of the CALL statement must be an alphanumeric item or a national item.

A procedure-name cannot be specified for the USING phrase in this CALL statement.

Identifier @1@ in the CANCEL statement must be an alphanumeric or a national item.

The content of @1@ in the SET statement cannot be changed by @2@. Specify a correct combination.

In the REPLACING phrase of the INITIALIZE statement, @1@ must be in a category that can be moved to an item of category @2@.

Item @1@ which is defined with an OCCURS clause with DEPENDING cannot be specified in an INITIALIZE statement.

@1@ in the PERFORM statement must be a numeric item.

@1@ in the PERFORM statement must be an integer item.

Identifier @1@ in the @2@ statement must be a data item that has an OCCURS clause with an INDEXED BY phrase.

@1@ of the VARYING phrase in the SEARCH statement must be an index-name, indexed data item, or integer item.

The two operands connected by the THROUGH phrase in the EVALUATE statement must be of the same class.

If an arithmetic expression, identifier, or literal is specified in the selection subject of the EVALUATE statement, the selection object must be an arithmetic expression, identifier, literal, or 'ANY'.

The two operands connected with the THROUGH phrase in the EVALUATE statement cannot be a Boolean or object identifier.

If 'TRUE' or 'FALSE' is specified in the selection subject of the EVALUATE statement, the selection object must be a conditional expression, 'TRUE', 'FALSE', or 'ANY'.

No corresponding items exist in the @1@ statement with CORRESPONDING phrase. The statement is ignored.

@2@ specified in the @1@ statement with the CORRESPONDING phrase must be a group item.

In the ACCEPT statement specifying a mnemonic-name or function-name, identifier @1@ must be a fixed-length group item, alphabetic item, alphanumeric item, external decimal item, internal decimal item, binary item, or external boolean item.

If a DATE, DAY, DAY-OF-WEEK, or TIME is specified in the FROM phrase of the ACCEPT statement, @1@ must be a fixed length group item, alphanumeric, alphanumeric edited, numeric edited, external decimal, or binary item.

@1@ @2@ cannot be specified to a @4@ phrase in a @3@ statement.

An alphabet-name corresponding to a function-name cannot be specified in the COLLATING SEQUENCE phrase of @1@.

@1@ defined in the CONSTANT SECTION cannot be specified in a receiving field.

Special register @1@ cannot be specified in a receiving field.

Operand @2@ in the @1@ statement must be a numeric item.

Operand @2@ of the GIVING phrase in the @1@ statement must be a numeric or a numeric edited item.

Corresponding item @2@ in the @1@ statement with the CORRESPONDING phrase must be an elementary numeric data item.

@1@ of the DIVIDE statement with the REMAINDER clause must be a fixed decimal point item or a decimal point literal.

Receiving item @1@ of the DIVIDE statement with a remainder must be a fixed decimal point item or a numeric edited item.

The literal of the boolean expression must be a boolean literal or ZERO. The literal is assumed to be ZERO.

The length of boolean items and boolean literals (except a boolean literal with 'ALL') must be the same.

Receiving operand @1@ with the [NOT] ON SIZE ERROR phrase must be a numeric item or a numeric edited item.

The expression to the right of the equals sign in a COMPUTE statement with the [NOT] ON SIZE ERROR phrase must be an arithmetic expression.

If the expression to the right of the equals sign in a COMPUTE statement is an arithmetic expression, receiving operand @1@ must be a numeric item or a numeric edited item.

If the expression to the right of the equals sign in a COMPUTE statement is a boolean expression, receiving operand @1@ must be a boolean item.

The expression to the right of the equals sign in a COMPUTE statement must be an arithmetic expression or a boolean expression.

Receiving operand @1@ of the COMPUTE statement must be a numeric item, a numeric edited item, or a boolean item.

Receiving items of the COMPUTE statement must be numeric items or numeric edited items, or they all must be boolean items.

The ROUNDED phrase cannot be specified for a COMPUTE statement containing a boolean item.

@1@(@2@) and @3@(@4@) cannot be compared.

A comparison between a literal and a literal cannot be done in a relation condition.

The relational operator for a comparison of boolean operands must be 'EQUAL(=)' or 'NOT EQUAL(NOT =)'.

In comparison between a Boolean operand and a Boolean operand other than an ALL boolean literal, the number of Boolean characters of both operands must be the same.

@1@ of the index comparison must be an integer.

For an @1@ check of a class condition, @2@ must be a group item, alphabetic item, alphanumeric item, alphanumeric edited item, or numeric edited item.

For a numeric check of a class condition, @1@ must be an external decimal item, internal decimal item, group item, alphanumeric item, alphanumeric edited item, or numeric edited item.

For a boolean check of a class condition, @1@ must be an external boolean item, group item, alphanumeric item, alphanumeric edited item, or numeric edited item.

For a class name check of a class condition, @1@ must be a group item, alphabetic item, alphanumeric item, alphanumeric edited item, or numeric edited item.

@1@ of the sign condition must be a numeric item.

The arithmetic expression of the sign condition must contain at least one identifier.

The usage of sending item @1@ in the UNSTRING statement must be 'DISPLAY'.

An item with a reference modifier cannot be specified for the sending operand of an UNSTRING statement.

The usage of identifier @2@ of the @1@ phrase in the UNSTRING statement must be 'DISPLAY'.

Identifier @1@ of the INTO phrase in the UNSTRING statement cannot be an alphanumeric edited item, numeric edited item, national edited item, or a numeric item having 'P' in its PICTURE character-string.

Identifier @2@ of the @1@ phrase of the UNSTRING statement must be an integer item.

If any of the operands in the DELIMITED BY phrase, INTO phrase, or DELIMITER IN phrase is a national type, then, in the UNSTRING statement on the sending side, the type for all must be national type and should have the same encoding.

Corresponding item @2@ is not unique in the @1@ statement with the CORRESPONDING phrase.

The usage of operand @2@ of the @1@ phrase in the STRING statement must be 'DISPLAY'.

An item with a reference modifier cannot be specified as a receiving area item in the STRING statement.

Item @2@ of the '@1@' phrase in the STRING statement must be an integer item.

The receiving item in the STRING statement cannot be an alphanumeric edited item, a numeric edited item, or a national edited item.

If any of the operands in the DELIMITED BY phrase or the INTO phrase is a national type, then on the sending side in the STRING statement, all operands must be National language and have the same encoding.

@1@ @2@ cannot be specified in the @3@ phrase of the OPEN statement.

File @1@ with the LINAGE clause cannot be specified in the EXTEND phrase of the OPEN statement.

The @1@ phrase can only be specified for a sequential file other than a print file with a FORMAT clause.

A @1@ phrase can only be specified for a sequential file other than a print file with a FORMAT clause. The @1@ phrase is ignored.

In the USING or GIVING phrase of the MERGE statement, a file cannot be specified more than once. File @1@ is ignored.

A file having a record description entry with a CHARACTER TYPE or PRINTING POSITION clause cannot be specified in the USING or GIVING phrase of the @2@ statement. File name @1@ is ignored.

Operand @1@ of the FROM phrase and record-name @2@ cannot occupy the same storage space.

The CONTROL AREA phrase cannot be specified for any file except a communication-file.

An ADVANCING phrase with a mnemonic-name cannot be specified in the WRITE statement for file @1@ with the LINAGE clause. BEFORE ADVANCING 1 is assumed.

The ADVANCING phrase can only be specified for a sequential file.

Operand @1@ of the ADVANCING phrase in the WRITE statement must be an integer item. ADVANCING 1 is assumed.

The integer of the ADVANCING phrase in the WRITE statement must be 0 through 32767. ADVANCING 1 is assumed.

The @1@ clause cannot be specified for @2@.

@1@ @2@ cannot be specified in a REWRITE statement.

The NEXT phrase cannot be specified for random access file @1@.

Operand @1@ of the INTO phrase and record area cannot occupy the same storage space.

The KEY phrase of the READ statement can only be specified for an indexed file of random access mode. The KEY phrase is ignored.

Data-item @1@ of the KEY phrase in the READ statement must be specified as a record key or an alternate record key.

The @3@ phrase cannot be specified in the READ statement for file @2@ of @1@.

A GO TO statement without a procedure-name must be referred to by an ALTER statement.

Identifier @1@ of the GO TO DEPENDING ON statement must be an integer item.

Paragraph @1@ referred to by the ALTER statement must be a sentence consisting of a single GO TO statement without a DEPENDING ON phrase.

Operand @1@ in the arithmetic expression must be a @2@.

Operand @1@ in the boolean expression must be a @2@.

Operand @1@ enclosed with parentheses in the expression must be a numeric item or a boolean item.

Data-name @1@ in parentheses for the subscript or reference modifier must be a @2@ which is an integer.

There is no valid data item in the REPLACING phrase of the INITIALIZE statement.

There is no item to be initialized by the INITIALIZE statement.

When a conditional expression of a selection subject is specified in the EVALUATE statement, the selection object must be a conditional expression, TRUE, FALSE, or ANY.

The KEY IS phrase must be specified in the data description entry of @1@ of the SEARCH ALL statement.

The data name in the WHEN phrase of the SEARCH ALL statement must be specified in the KEY IS phrase of the data description entry of @1@.

The rightmost subscript of the WHEN phrase in the SEARCH ALL statement must be the first index-name related to @2@.

All data-names or condition-names specified in the KEY IS phrase must be specified as data-names or condition-names in the WHEN phrase of the SEARCH ALL statement.

@1@ @2@ cannot be specified in a DELETE statement.

For sequential access to file @1@, the @2@ phrase cannot be specified in a DELETE statement.

@1@ @2@ @3@ cannot be specified in a START statement.

An item which is not specified in a RELATIVE KEY clause cannot be specified in a KEY phrase of a START statement with a relative file.

An item which is not specified in a RECORD KEY clause or an ALTERNATE RECORD KEY clause, or an item which is subordinate to it, cannot be specified in a KEY phrase of a START statement with an indexed file.

The USAGE of sending item @1@ in the STRING statement must be DISPLAY.

A key item cannot be specified in both the left and right parts of a conditional expression in a WHEN phrase or an AND phrase in a SEARCH ALL statement.

An ADVANCING PAGE phrase and an END-OF-PAGE phrase cannot both be specified in the same WRITE statement. It is accepted as written: the compiler will generate code for both ADVANCING PAGE and END-OF-PAGE.

A national item or a national edited item with a CHARACTER TYPE phrase or a file which includes an item with a PRINTING POSITION phrase cannot be specified in a REWRITE statement.

Inspected item @1@ in the INSPECT statement must be an item with a USAGE of DISPLAY.

Tallying item @1@ in the INSPECT statement must be a numeric item.

For a CHARACTERS phrase in an INSPECT statement, the length of the replaced character and scope specifying character must be 1. The statement is ignored.

For a REPLACING phrase in an INSPECT statement, the lengths of the replacing character and replaced character must be equal.

For a CONVERTING phrase in an INSPECT statement, if the converted character is a national or a national edited item, the converting character and the converted character cannot exceed 65536 in length. Non-national items cannot exceed 256 in length.

For a CONVERTING phrase in an INSPECT statement, the lengths of the converting character and the converted character must be equal.

In the INSPECT statement, items other than the tallying item and the inspecting item must all be national items or national edited items, or non-national items.

Items other than the item being inspected and the tallying item in INSPECT statement must have a USAGE of DISPLAY.

@1@ @2@ cannot be specified to a USING phrase in a CALL statement.

@1@ in the SEARCH ALL statement cannot be reference modified.

In the INSPECT statement, all items being inspected must be of the same encoding scheme, except for the TALLYING item.

@2@ @3@ with access mode @1@ cannot be specified for a @4@ phrase of an OPEN statement.

File @2@ cannot be specified in the @1@ statement more than once. Only the first specification is accepted.

(CONF) A 'WRITE' statement with an ADVANCING phrase and a WRITE statement with no specification are coded for the same file. 'AFTER ADVANCING 1' is added to the WRITE statement without an ADVANCING phrase.

(CONF) A 'DELIMITED BY' phrase with 'ALL' and a 'DELIMITER IN' phrase are both specified. If there is a string of delimiters in the sending item, one delimiter is moved to the item of 'DELIMITER IN' phrase.

A 'RELATIVE KEY' clause must be specified for relative file @1@.

(CONF) The order of increment for an identifier in a PERFORM statement is as follows. (1) The present value of the 'BY' phrase is added to the identifier of the VARYING phrase. (2) The identifier of the 'AFTER' phrase is set to the present value of the 'FROM' phrase.

(CONF) An alphabetic check is specified. Lowercase alphabetic characters are considered to belong to the alphabetic class.

(CONF) An item subordinate to a FILLER item satisfies the CORRESPONDING phrase in the @1@ statement. It is assumed to be a corresponding item.

(CONF) Numeric item @1@ with a 'P' on the left of the decimal point is compared with a nonnumeric operand. A numeric item without a 'P' on the left of decimal-point is assumed.

Item @1@ including an item with a CHARACTER TYPE phrase or PRINTING POSITION phrase specified in a 'FROM' phrase in a WRITE statement must not have a reference modifier.

@1@ (@2@) and @3@ (@4@) cannot be compared.

The record length of file @3@ specified in the @2@ phrase of the @1@ statement cannot exceed the maximum record length of the sort-merge file, and cannot be less than the sort-merge file minimum record length.

Data item @2@ of the KEY phrase in the @1@ statement can be any fixed-length item except internal boolean or external boolean without subscripting.

@1@ and @2@ (@3@) cannot be compared.

@1@ (@2@) and @3@ cannot be compared.

@1@ and @2@ (@3@) cannot be compared.

@1@ (@2@) and @3@ cannot be compared.

@1@ and @2@ cannot be compared.

The computation results in zero being raised to the power of a negative integer literal. The value zero comes from a numeric literal with value 0, the figurative constant ZERO, or a computation in which no significant digits will reach the intermediate result. The result is assumed to be zero.

The integer exponent is greater than 9 digits. The exponent is assumed to be the 9 low order digits.

File @1@ with the RECORD CONTAINS 0 CHARACTERS clause cannot be specified in an OPEN statement with an OUTPUT phrase.

Key item @1@ and the comparison object in the SEARCH ALL statement cannot be boolean items (literal).

An item with a reference modifier cannot be specified in a @1@ statement with a CORRESPONDING phrase.

The record length of the sort-merge file specified in the @1@ statement must be less than or equal to the maximum record length of file @3@ specified in the @2@ phrase, and greater than or equal to its minimum record length.

(CONF) WRITE statements without ADVANCING phrases are specified for files with LINAGE clauses. 'AFTER ADVANCING 1' is assumed.

When indexed file @2@ is specified in a GIVING phrase of a @1@ statement, data-name @3@ of the KEY phrase must exist in the same character position as the data item of the prime record key of the file.

When a national item or a national edited item is specified in the KEY phrase of a @1@ statement, the COLLATING SEQUENCE phrase cannot be specified.

(CONF) A file with a control character is specified in the READ statement. The record including the control character is read.

The number of subscripts for @1@ of the 'WHEN' phrase in the SEARCH ALL statement must be @2@.

When report-name @1@ is specified in a GENERATE statement, a 'CONTROL' clause must be specified in the report description entry.

If report-name @1@ is specified in a GENERATE statement, plural detail report groups cannot be specified in the report description entry.

Report-name @1@ specified in a GENERATE statement must have one or more body groups in its report description entry.

Data name @1@ in the GENERATE statement must be the name of a detail report group.

Report file @1@ cannot be specified for a statement except for an OPEN OUTPUT, OPEN EXTEND, CLOSE, or USE statement.

@1@ of the nonnumeric comparison must be an integer. The decimal-point is assumed to be on the rightmost side.

The receiving item in the STRING statement cannot be a item with a JUSTIFIED clause. The items is assumed to not have a JUSTIFIED clause.

Identifier @2@ of a @1@ phrase in an UNSTRING statement cannot be an external floating-point item.

In a SEARCH ALL statement, when either key item @1@ or a comparison object is an integer item with P, another object cannot be an alphabetic, alphanumeric, alphanumeric-edited, numeric-edited, nonnumeric-literal, or a figurative constant other than ZERO.

Key item @1@ and the comparison object in the SEARCH statement with ALL cannot exceed 256 bytes in length.

(CONF) The numeric literal '-0' is specified as a sending item in a MOVE statement. '+0' is assumed.

@1@ must be defined in the BASED-STORAGE SECTION.

Argument @1@ cannot be specified to @2@.

If a record containing a RECORD clause with a DEPENDING ON phrase is specified in a WRITE statement, an item containing a CHARACTER TYPE or PRINTING POSITION clause cannot be specified in the FROM phrase.

An ADVANCING phrase cannot be specified to a WRITE statement for control record @1@.

Data item @1@ specified in the BASED-STORAGE SECTION must be qualified by a pointer expression.

Pointer data item @1@ cannot be specified in the @2@ statement.

The relational operator for comparison of pointer data operands must be 'EQUAL(=)' or 'NOT EQUAL(NOT =)'.

Data name @1@ defined in the BASED-STORAGE SECTION cannot be specified in the @3@ phrase of the @2@ statement.

@2@ is an unsigned numeric item or a numeric edited item without editing sign control symbols in the @1@ statement. A negative value cannot be moved.

When @2@ is moved to @3@ in the @1@ statement, there are no overlapping digits.

When a numeric literal is moved to @2@ in the @1@ statement, digit overflow may occur.

When a numeric literal is moved to @2@ in the @1@ statement, the decimal part is truncated.

When a numeric literal is moved to numeric item @2@ with scaling position character 'P' in the @1@ statement, the value of the character position corresponding to 'P' of the numeric item is not reflected.

When @2@ is moved to @3@ in the @1@ statement, the value of the sending item is not reflected in the receiving item.

The number of parameters specified in the USING phrase of the CALL statement must be the same as the number of parameters specified in the USING phrase of the PROCEDURE DIVISION.

The type of parameter @2@ specified in the USING phrase or the RETURNING phrase of the CALL statement must be the same as the type of parameter @3@ specified in the PROCEDURE DIVISION USING phrase or the RETURNING phrase of program @1@.

The length of parameter @2@ specified in the USING phrase or RETURNING phrase of the CALL statement must be the same as the length of parameter @3@ specified in the PROCEDURE DIVISION USING phrase or RETURNING phrase of program @1@.

(CONF) The subscript or reference modifier is evaluated only one time immediately before execution in the UNSTRING statement.

A nonnumeric literal that contains a period was moved to a numeric item or a numeric edited item. The characters following the period are ignored in the nonnumeric literal.

(OBS) Moving all literals of two or more characters to a numeric item or a numeric edited item is an obsolete feature in @1@ COBOL. It is accepted as written.

(OBS) Comparing all literals of two or more characters with a numeric item or a numeric edited item is an obsolete feature in @1@ COBOL. It is accepted as written.

SET statement item @1@ of the @2@ phrase must be an index-name, index data item, integer item, pointer data item, NULL, address of special register, or object reference data item.

SET statement receiving item @1@ must be an index-name, index data item, integer item, pointer data item, address of special register, or object reference data item.

Data-name @1@ of the pointer qualifier must be a pointer data item.

The special register for the presentation file cannot be created using data-name @1@ in the BASED-STORAGE SECTION.

@1@ being tested by KANJI or DBCS class condition must be a national item or a national-edited item.

Data-name @1@ is qualified by an implicit pointer over 7 times, or qualified recursively.

When a mnemonic-name corresponds to function-name @1@, @2@ must be an unsigned integer item or an unsigned integer.

When a mnemonic-name corresponds to function-name @1@, @2@ must be a fixed length group item, an alphanumeric elementary item, or a nonnumeric literal.

The argument of @1@ must be a type integer.

Argument @1@ of @2@ must be a type alphabetic or an alpha-numeric.

Argument @1@ of @2@ must be a type numeric.

@1@ must be an unsigned integer item.

@1@, which is a BY VALUE parameter of the CALL statement, must be one of: a binary item with a usage of COMP-5, BINARY-CHAR, BINARY-SHORT, or BINARY-LONG and is 4 bytes or less; or a 1 byte item; or a numeric literal that has 9 digits or less.

The file that is specified in the UNLOCK statement must be a sequential file, a relative file, or an indexed file.

All arguments of @1@ must be of the same type.

The numeric parts of the argument of @1@ cannot exceed 18 digits.

The argument of @1@ must be greater than or equal to 0.

The first argument of the FUNCTION PRESENT-VALUE must be greater than -1.

The numeric function cannot be reference modified. An alphanumeric function is assumed.

An integer function and a numeric function cannot be specified in the @1@ statement.

@1@ in the PERFORM statement must be an integer or an integer item.

An integer function and a numeric function cannot be specified in a FROM clause in a @1@ statement.

An integer function and a numeric function cannot be specified in the DELIMITED phrase of a @1@ statement.

An integer function and a numeric function cannot be specified in an INSPECT statement.

An integer function and a numeric function cannot be specified in the @1@ statement.

Indexed file @2@ with ACCESS MODE IS RANDOM specified and WITH DUPLICATES specified to prime key cannot be specified in a @1@ statement.

The argument format of @1@ is invalid.

The argument of FUNCTION CHAR exceeds the maximum number of characters.

The argument value of @1@ must be between -1 and +1.

The first argument value of @1@ must be greater than or equal to 0.

The second argument value of @1@ must be an integer greater than 0.

The second argument value of @1@ must not equal 0.

The argument value of @1@ must be greater than 0.

The argument of @1@ must be a type alphabetic or a type alphanumeric, and must be one character.

The types of argument in @1@ must be alphabetic, alphanumeric or numeric.

The argument of @1@ must be a nonnumeric literal or an alphanumeric item.

The argument of @1@ must be a nonnumeric literal or an alphanumeric item. An alphanumeric item is assumed.

@1@ in the PERFORM statement must be a numeric literal or a numeric item.

The argument of @1@ must be a fixed decimal point item or a decimal point literal.

The WITH phrase cannot be specified in a PROCEDURE DIVISION of a contained program or a CALL statement for a contained program.

In this system, PASCAL LINKAGE cannot be used. STDCALL LINKAGE is assumed.

In this system, PASCAL LINKAGE or STDCALL LINKAGE cannot be used. C linkage is assumed.

In the @1@ statement, @2@ of the PROMPT phrase must be a one character alphabetic item, alphanumeric item, national item, nonnumeric literal, or national character literal.

@2@ of the AT phrase must be a numeric item with USAGE IS DISPLAY, or a numeric literal of 4 or 6 digits.

The item length of @2@ cannot be variable in the @1@ statement.

The PREVIOUS phrase of the READ statement can only be specified for an indexed file or a relative file of dynamic access mode.

@1@ being tested by the @2@ class condition must be an alphabetic, alphanumeric, alphanumeric-edited, numeric-edited, national or national-edited item.

Argument @1@ of FUNCTION CAST-ALPHANUMERIC must be a national item or a national-edited item.

Argument @1@ of FUNCTION NATIONAL must be an alphabetic, alphanumeric, alphanumeric-edited, numeric-edited or external decimal item.

@1@ of the DISPLAY statement must be defined in the WORKING-STORAGE SECTION.

@1@ of the ACCEPT statement must be defined in the WORKING-STORAGE SECTION.

@2@ of the @1@ statement cannot be specified as a group item.

If @2@ in the @1@ statement is a numeric item or a numeric edited item, the SIZE phrase cannot be specified.

If @2@ in the @1@ statement is specified with the JUSTIFIED clause, the SIZE phrase cannot be specified.

If a numeric literal is specified in the @1@ statement, the SIZE phrase cannot be specified.

@2@ must be an alphanumeric item, a national item, an alphanumeric literal, or a national literal when untyped object reference identifier @1@ is specified in an INVOKE statement.

Method @2@ cannot be invoked by @1@.

The BY CONTENT phrase cannot be specified in the INVOKE statement when an untyped object reference identifier, special class object reference identifier, or special class class-name @1@ is specified in the INVOKE statement.

@1@ must conform to @2@.

The relational operator for the comparison of object reference identifiers must be EQUAL(=) or NOT EQUAL(NOT =).

A 'RETURNING' phrase must be specified for a CALL statement which calls @1@. There is a RETURNING phrase in the PROCEDURE DIVISION of program @1@.

A 'RETURNING' phrase is not specified in the PROCEDURE DIVISION for method @1@.

In-line invocation method @1@ does not have a RETURNING phrase. Figurative constant zero is assumed.

@1@ cannot be reference modified.

The property accessor (GET method) is not defined.

The property accessor (SET method) is not defined.

An @1@ cannot be specified as a receiving field except in a MOVE or SET statement.

An object identifier cannot be specified in a @1@ statement.

Group item @1@ that includes an object reference cannot be specified.

The parameter number specified in the USING phrase of the INVOKE statement or in-line invocation must be the same parameter number specified in the USING phrase of the PROCEDURE DIVISION.

BY REFERENCE phrase items, RETURNING phrase items in an INVOKE statement, and argument items of in-line invocation cannot be reference modified.

Moving all literals of two or more characters to a numeric item or a numeric edited item is an obsolete feature in @1@ COBOL.

Comparing all literals of two or more characters with a numeric item or a numeric edited item is an obsolete feature in @1@ COBOL.

The class-name of a special class cannot be specified in a conditional expression.

The object reference identifier in the @1@ statement cannot refer to a special class except *COM(OLE)-EXCEPTION.

An in-line method invocation, or object property that returns object reference data, cannot be specified in a conditional expression.

The XREF listing will not be output because severity code S errors have been encountered.

Internal boolean item @1@ must be defined so that it starts on a byte boundary.

When an ANY LENGTH clause is specified to a formal parameter, the USING parameter of the INVOKE statement or the argument of the in-line method invocation corresponding to its formal parameter must be a parameter for which the BY REFERENCE phrase is specified or a nonnumeric literal or national character literal except for ALL literal.

Data-item @1@ with an ANY LENGTH clause cannot be specified in a USING or a RETURNING phrase of a @2@ statement.

Data-item @1@ with an ANY LENGTH clause cannot be specified in a RETURNING phrase of a @2@ statement.

Data-item @1@ with an ANY LENGTH clause cannot be specified in an argument of @2@.

Data-item @1@ with an ANY LENGTH clause cannot be specified in an INITIALIZE statement.

Indirect reference class '@1@' must be specified in a repository paragraph.

Data-item @1@ with an ANY LENGTH clause cannot be specified in a BY CONTENT phrase of an INVOKE statement.

Method @1@ for which the ANY LENGTH clause is specified for an item of the RETURNING phrase in the PROCEDURE DIVISION header cannot be invoked by an in-line invocation.

@1@ in the RAISING phrase of the @2@ statement must be an object reference identifier. It must refer to a class name that is specified in the RAISING phrase of the PROCEDURE DIVISION header.

An EXIT METHOD statement with a RAISING phrase cannot be specified in a _FINALIZE method.

The result of the MOVE is undefined because the area of sending item @1@ and the area of receiving item @2@ overlap.

@2@ (@3@) is specified for a formal parameter of @1@ type. Sending and receiving may not function correctly.

The OMITTED phrase can only be specified for a parameter of a COM server method that has an optional attribute.

The OMITTED phrase can only be specified as a parameter if @1@ is a special class object reference identifier.

@1@ must be conformed to @2@ (@3@ type).

A figurative constant and the ALL literal cannot be specified for the parameter of a special class method.

@2@ (@3@) is specified for a formal parameter of @1@ type.

Data-name @1@ of the CONTROL phrase cannot be an alphanumeric item in the @2@ statement.

If the @1@ argument of FUNCTION UCS2-OF is either an alphabetic, alphanumeric or alphanumeric-edited item, then the encoding format must be UTF8.

If the '@1@' argument of FUNCTION UTF8-OF is either a national item or a national-edited item, then the encoding format must be UTF16.

Argument @1@ of FUNCTION STORED-CHAR-LENGTH must be an alphabetic, alphanumeric, alphanumeric-edited, national or national-edited item.

If compile option RCS(UTF16) or ENCODE is specified, then the size is not compared as a national language when the national part of the group item @1@ includes a national item.

When receiving item @2@ is a strongly-typed group item, sending item @1@ must be a strongly-typed group item of the same type as @2@.

If either data item is a strongly-typed group item, both data items must be of the same type.

If @2@ of an INTO phrase in a @1@ statement is a strongly-typed group item, @3@ must have one record description.

When a strongly-typed group item specified in a USING or RETURNING phrase of an INVOKE statement, or specified in an argument of an in-line method invocation, the group item must be level number 01.

A strongly-typed group item @1@ is specified in a place where it cannot be specified.

Strongly-typed items, or elementary items that are subordinate to strongly-typed group items (other than those of alphanumeric or national categories), cannot be reference modified.

An in-line method invocation, or an object property whose returning item is a strongly-typed group item containing object reference data, cannot be specified in a conditional expression.

If compile option RCS(UTF16) or ENCODE is specified, then it cannot be called correctly if the group item @1@, which includes the national item, is specified as a calling name.

If compile option RCS(UTF16) or ENCODE is specified, then the size is not compared as a national language when the national part of the group item @1@ includes a national item.

If compile option RCS(UTF16) or ENCODE is specified, then in the group item @1@, which includes the national items, the national language part is not displayed as national language in the DISPLAY statement.

When compile option RCS(UTF16) or ENCODE is specified, then a WRITE statement of a line sequential file cannot contain both a national item and a group item @1@.

An EXIT statement with a SECTION phrase can only be specified in a section.

@1@ defined in the LINKAGE SECTION must be specified in a USING phrase or a RETURNING phrase of the PROCEDURE DIVISION, or in a USING phrase of an ENTRY statement.

For the main program, the parameter specified for the USING phrase of the PROCEDURE DIVISION header should be only one group item which does not exceed 102 bytes, and the first subordinate elementary item must be a 2 byte binary item.

@1@ of BY VALUE in the CALL statement must be one of: a binary item with USAGE COMPUTATIONAL-5 with a length not exceeding 8 bytes; a one byte item; or a numeric literal of 18 digits or fewer.

The group item @1@ that only contains elementary items that are single precision floating-point items cannot be specified in the RETURNING phrase of the @2@ statement.

Type-name @1@ cannot be an operand in a comparison.

A 'RETURNING' phrase cannot be specified for a CALL statement which calls @1@. There is no RETURNING phrase in the PROCEDURE DIVISION of program @1@.

The numeric literal of the sending item exceeds the range of @2@. Its numeric literal cannot be moved to @1@.

The type of argument-1 of @1@ must be an alphabetic, alphanumeric or national, and it must not be a group item.

The argument-2 of @1@ must be of an alphanumeric category.

Argument-1 of FUNCTION DISPLAY-OF must be of the national class.

In the FUNCTION DISPLAY-OF argument-2, if the character type is alphanumeric or alphabetic and the length is 1, the encoding format must be the same as the selected compile option for ENCODE.

Argument-1 of FUNCTION NATIONAL-OF must be of the alphabetic or alphanumeric class.

If the FUNCTION NATIONAL-OF argument-2 is a national language item type and the length is 1 character, the encoding format must be same as the selected compile option for ENCODE.

Non-USAGE DISPLAY item, numeric edited item, alphanumeric edited item, national edited item, external boolean item, external floating-point item, numeric item that symbol 'P' exists in picture clause, and group item including either the above-mentioned cannot be specified in @2@ of @1@ statement with CSV-FORMAT or TSV-FORMAT. @3@ is ignored.

@4@ that is item with a @3@ clause or the group item including it cannot be specified in @2@ of @1@ statement with CSV-FORMAT or TSV-FORMAT. @4@ is ignored.

@3@ that is item of @2@ of @1@ statement with CSV-FORMAT or TSV-FORMAT should be an alphanumeric item without JUSTIFIED and ANY LENGTH clause.

@3@ that is item of POINTER phrase of @1@ statement with CSV-FORMAT or TSV-FORMAT should be an integer item that is without the symbols 'P' in PICTURE clause, and the value in which 1 is added to length of @2@ should be a range of the value of its item.

@2@ cannot be specified in @1@ statement with CSV-FORMAT or TSV-FORMAT.

A numeric item exceeding 18 digits exists in the USING or RETURNING phrase of the @1@'@2@'. The numeric item cannot be used in 18-digit mode.

The number of digits in the arithmetic expression intermediate result exceeds the maximum allowed in 18-digit mode.

The floating point attribute is applied to the intermediate result of the arithmetic expression in 31-digit mode.

The encoding of the target to be compared and the @1@ key item in the SEARCH ALL statement must be the same.

Different encoding cannot be given for the comparison of multiple data items.

Different encoding cannot be given for the move of multiple data items.

When compilation option RCS(UTF16) or ENCODE is specified, @1@ cannot be specified in a WRITE statement for a print file. @1@ is different from the encoding of the print file.

The length of the national hexadecimal nonnumeric literal for encoding UTF32 must be a multiple of 8.

In the '@1@' group item, which is specified in the argument of @2@, National items having different encoding formats are included. The '@1@' national item is taken as the Encoding's alphanumeric data item.

In the CONVERSION specification MOVE statement, '@1@' cannot be specified in the items that are specified by the @2@ clause.

A '@1@' having the same encoding as the receiving side cannot be moved to '@2@'.

Move cannot be performed because the area of receiving side item '@2@' and the area of sending side item '@1@' are overlapping.

Method '@1@' was defined with the OVERRIDE clause, but no method of that name was found in the parent class. The OVERRIDE phrase is ignored.

Method '@1@' is defined multiple times. The method-name must be unique in @3@ '@2@'.

Method '@1@' that is defined or overridden in class '@2@' cannot override. The method '@1@' definition is ignored.

The method prototype definition of '@1@' is missing. Method '@1@' is ignored.

Property-name '@1@' cannot be a data-name with a PROPERTY clause.

Property-name '@1@' specified in the property-specifier is undefined. The property-specifier is ignored.

Property-name '@1@' specified in the property-specifier is defined multiple times. The property-specifier is ignored.

The class-name specified in the @1@ clause is invalid. The class-name is ignored.

The @1@ clause can only be specified in a program definition. The @1@ clause is ignored.

The @1@ clause cannot be specified with a @2@ clause. The @1@ clause is ignored.

The @1@ clause can only be specified in WORKING-STORAGE SECTION or LINKAGE SECTION. The @1@ clause is ignored.

The @1@ clause can only be specified in WORKING-STORAGE SECTION, LOCAL-STORAGE SECTION or LINKAGE SECTION. The @1@ clause is ignored.

The @1@ clause cannot be specified for a group item. The @1@ clause is ignored.

A condition-name cannot specified for a data item in the LINKAGE SECTION of the method prototype definition. The condition-name is ignored.

A @1@ clause cannot be specified for an item with an OCCURS clause or its subordinate item. The @1@ clause is ignored.

An item redefined by a REDEFINES clause cannot have a @1@ clause, or cannot be subordinate to a data item with a @1@ clause. The REDEFINES clause is ignored.

The data-name in the RENAMES clause or in the THROUGH phrase cannot have a @1@ clause, or cannot be subordinate to a data item with a @1@ clause. The RENAMES clause is ignored.

The USAGE OBJECT REFERENCE SELF clause can only be specified in a FACTORY definition or a FACTORY method definition. SELF is ignored.

The USAGE OBJECT REFERENCE @1@ OF SELF clause can only be specified in an object definition or an object method definition. @1@ OF SELF is ignored.

The @1@ clause cannot be specified in DATA DIVISION of a factory definition or object definition. The @1@ clause is ignored.

The @1@ clause cannot be specified in an item with an OCCURS DEPENDING ON clause. The OCCURS DEPENDING ON clause is ignored.

The item specified in the @1@ clause cannot be subordinate to a data item with an OCCURS DEPENDING ON clause. It is accepted as written.

The @1@ clause cannot be specified in a variable address item. It is accepted as written.

The @1@ clause cannot be specified for an item specified in an EXTERNAL clause or for its subordinate item. It is accepted as written.

The @1@ clause cannot be specified for a subordinate item with a REDEFINES clause. It is accepted as written.

The @1@ clause can only be specified for the item that is unique with no qualifiers. The @1@ clause is ignored.

The @1@ clause cannot be specified for a pointer data item. The @1@ clause is ignored.

The data item specified in the @1@ clause cannot appear between a data item in a RENAMES clause and a data item in a THROUGH phrase. The RENAMES clause is ignored.

The @1@ clause cannot be specified for an object reference data item with SELF, FACTORY OF SELF, or CLASS OF SELF. The @1@ clause is ignored.

If a special class is specified in the @1@ clause, another optional phrase cannot be specified. Other OPTIONAL phrase is ignored.

A 'CHARACTER TYPE' clause with a DEPENDING ON phrase cannot be specified in the DATA DIVISION of @1@.

The @1@ clause cannot be specified in the LINKAGE SECTION of a method prototype definition or a separate method definition. The @1@ clause is ignored.

A condition-name cannot be specified for an object reference data item.

The LINAGE clause can only be specified with an EXTERNAL clause in a program definition. The LINAGE clause is ignored.

The data-name in the @1@ clause cannot be an object reference data item or a group item which contains an object reference data item.

The ANY LENGTH clause cannot be specified for a data-item without a PICTURE clause. PICTURE X is assumed.

A data-item with an ANY LENGTH clause can only be specified in a PICTURE clause. It is ignored, and the compiler skips to the next level-number, section or division.

An ANY LENGTH clause cannot be specified for a data-item in a get property method or a set property method. The ANY LENGTH clause is ignored.

An ANY LENGTH clause cannot be specified for a group item. The ANY LENGTH clause is ignored.

Data-name @2@ in the @1@ clause cannot have an ANY LENGTH clause.

The data-name of the ASSIGN clause in file-name '@1@' cannot be an item with an ANY LENGTH clause, a group item that includes an object reference item, or a strongly typed item.

A condition-name cannot be specified for a data-item with an ANY LENGTH clause.

The data-name in @1@ cannot be an object reference data item or a group item which contains an object reference data item.

A strongly-typed group item cannot be specified for the parameter of a get property method or a set property method. The specified parameter is ignored.

'@1@' specified in the TYPE clause must be a unique type-name. The TYPE clause is ignored.

The definition of type-name '@1@' refers to type-name '@2@'. '@1@' is ignored.

The TYPE clause cannot be specified for an item subordinate to a group item that has a USAGE clause, SIGN clause, SYNCHRONIZED clause, or CHARACTER TYPE clause. It is accepted as written.

The @1@ clause cannot be specified for an item specified in a TYPEDEF clause or for its subordinate item. The @1@ clause is ignored.

The data name specified for the @1@ clause cannot be an item which expands from the type. The @1@ clause is ignored.

A value is specified for a type that already has a value. It is accepted as written.

The level numbers of items subordinate to the item specified by the type declaration exceed @1@. The items with invalid level-numbers are ignored.

A type which is referred to by a conditional variable, must be defined as an elementary item. The condition-name is ignored.

A type which is referred to by a conditional variable cannot have a condition-name. The condition-name is ignored.

When a TYPE clause is specified for the first elementary item within a group item with a REDEFINES clause, the redefined item must be adjusted to an 8 byte boundary. The TYPE clause is assumed to be valid, but no slack bits are inserted and the object file is not created.

A type which is referred to by a variable-address item must be defined as an elementary item. Boundary not adjusted.

The type declared in the class definition which has an OCCURS clause with 'DEPENDING ON' or 'KEY IS' cannot be referenced in a separate method. The TYPE clause is ignored.

A type declaration with a STRONG phrase must be a group item. The STRONG phrase is ignored.

A type declaration with a STRONG phrase or a strongly typed item cannot contain a @1@ clause.

A strongly typed item cannot be defined in the BASED-STORAGE SECTION. A weakly typed item is assumed.

A type declaration with a STRONG phrase can only be referred by a level 01 data item or by an item that is subordinate to a type declaration with a STRONG phrase. A weakly typed item is assumed.

Data-name @2@ in the @1@ cannot be a strongly typed item.

The TYPEDEF clause has a STRONG phrase that cannot be specified with a TYPE clause. The STRONG phrase is ignored.

If the runtime code set of national data is unicode, data-name '@2@' in the @1@ clause cannot be a group item that contains a national item. It is accepted as written.

If the runtime code set of national data is unicode, the line sequential file record cannot have both national and non-national items.

Group item '@2@' which contains a national item is specified as a data-name of the @1@ clause. If the runtime code set of national data is unicode, the national part of this item is not compared as national.

Data-name @2@ in the @1@ clause cannot have a @3@ clause.

Compiler restriction. Total size of data items, and compiler generation area exceeds maximum value. Compilation terminated.

The program size is too large for this system. Compilation terminated. The program should be separated into proper size programs.

The identifier in the @1@ statement must be a specified object reference identifier.

An @2@ phrase cannot be specified in a @1@ statement.

An object property or in-line method invocation cannot be specified in the USING phrase of the @1@ statement. The @1@ statement is ignored.

Method-name '@3@' specified for @1@ is not defined in class '@2@'. @1@ is ignored.

The identifier in the RAISING phrase of the @1@ statement must be an object reference identifier.

The @1@ statement can only be specified in a program definition.

@1@ cannot be specified for a receiving item.

The @1@ phrase and the @2@ phrase cannot be specified simultaneously. The @2@ phrase is ignored.

The @1@ phrase cannot be specified in the PROCEDURE DIVISION of a method definition.

A RETURNING phrase can only have one operand.

Operand '@1@' in the @2@ phrase must be defined in the LINKAGE SECTION of this source unit as a level 01 or 77 item without a REDEFINES clause.

'@1@' is already specified as the operand in the USING phrase.

SELF, FACTORY OF SELF, and CLASS OF SELF cannot be specified as operand '@1@' in a USING phrase of a PROCEDURE DIVISION.

The operand in the RETURNING phrase cannot be the same as the operand in the USING phrase.

The @2@ phrase cannot be specified in the PROCEDURE DIVISION header of @1@.

DECLARATIVES cannot be specified in the PROCEDURE DIVISION of @1@.

An EXIT PROGRAM statement cannot be specified in a method definition.

An EXIT METHOD statement can only be specified in a method definition.

'@1@' must be the class-name that is specified in the REPOSITORY paragraph.

Class-name '@1@' cannot be the name of a special class.

The identifier specified immediately after @1@ must be an object identifier. The @1@ statement is ignored.

The method-name specified in the INVOKE statement must be an identifier, nonnumeric literal, or national character literal. The INVOKE statement is ignored.

If identifier '@1@' is specified in an INVOKE statement, the identifier specified immediately after INVOKE must be an identifier specified untyped OBJECT REFERENCE clause. The INVOKE statement is ignored.

A pointer data item cannot specified for the RETURNING phrase in a PROCEDURE DIVISION of a method definition.

Predefined object identifier SUPER can be used to invoke a method in the INVOKE statement or in-line method invocation, or as the object in an object property. The @1@ statement is ignored.

Predefined object identifier @1@ cannot be used in a program definition. Untyped object reference data item 'UNTYPED-OBJECT' is assumed.

Predefined object identifier SUPER must specify a class-name in the class which inherits multiple classes. Untyped object reference data item 'UNTYPED-OBJECT' is assumed.

Predefined object identifier SUPER cannot be used in a class that does not inherit any class. Untyped object reference data item 'UNTYPED-OBJECT' is assumed.

Predefined object identifier EXCEPTION-OBJECT can only be used in DECLARATIVES that correspond to the USE statement with class-name. Untyped object reference data item 'UNTYPED-OBJECT' is assumed.

@2@ cannot be specified in a @1@ statement. The @1@ statement is ignored.

A class-name that is specified in predefined object identifier SUPER must be specified in an INHERITS clause. Untyped object reference data item 'UNTYPED-OBJECT' is assumed.

The PROCEDURE DIVISION of a get property or set property method is missing a required parameter. An alphanumeric item of 1 character is assumed.

Only one @2@ parameter can be specified in a PROCEDURE DIVISION for a method definition with a @1@ phrase.

The identifier used to invoke a method in an in-line method invocation must be an object reference identifier. The in-line method invocation is ignored.

An object modifier cannot be specified for predefined object identifier SUPER or NULL.

An object modifier must be a specified class-name or universal. Universal is assumed.

@1@ cannot be used to invoke a method in an in-line method invocation or as the object in an object property.

The identifier in @1@ must be the object reference that refers to the class specified in the REPOSITORY paragraph.

Only a PROCEDURE DIVISION header can be specified in the PROCEDURE DIVISION of @1@.

The USE FOR DEAD-LOCK statement can only be specified in a program definition.

The interface for method '@1@' must conform to that of the overridden method. Method '@1@' is ignored.

There is no PROCEDURE DIVISION header in @1@. A PROCEDURE DIVISION header is assumed.

The class-name specified in the RAISING phrase of the PROCEDURE DIVISION header must have the same specifier as defined in the prototype method. It is accepted as written.

Only the method definition can be specified in the PROCEDURE DIVISION of @1@.

'@2@' specified in a @1@ statement cannot be specified in a USING phrase. The @1@ statement is ignored.

A literal, predefined object identifier, or class-name cannot be specified for the BY REFERENCE phrase of the @1@ statement. The @1@ statement is ignored.

A conditional phrase cannot be specified in the @1@ statement. The @1@ statement is ignored.

The ordinal position of the USING phrase for the @1@ statement is invalid. The @1@ statement is ignored.

The RETURNING phrase identifier for the @1@ statement must be defined in a file, WORKING-STORAGE, or LINKAGE SECTION. The @1@ statement is ignored.

The RETURNING phrase identifier for the @1@ statement must be defined in the FILE, WORKING-STORAGE, LOCAL-STORAGE or LINKAGE SECTION. The @1@ statement is ignored.

The method result for the identifier in the INVOKE statement must be the object identifier.

The interface for the separate method definition must conform to that for the method prototype.

The RETURNING phrase cannot be specified in the program definition PROCEDURE DIVISION containing an ENTRY statement. The RETURNING phrase is ignored.

Method-name '@2@' specified in @1@ is undefined in the parent class or the class that is inherited in the parent class. @1@ is ignored.

The method-name specified in an in-line method invocation must be a nonnumeric literal or a national character literal. The in-line method invocation is ignored.

@1@ cannot be specified as an argument of @2@.

@1@ cannot be specified as the @2@ identifier.

Property-name '@1@' is @2@.

The data item for the argument of the in-line method invocation must be defined in the FILE SECTION, WORKING-STORAGE SECTION or LINKAGE SECTION.

The data item for the argument of the in-line method invocation must be defined in the FILE SECTION, WORKING-STORAGE SECTION, LOCAL-STORAGE SECTION or LINKAGE SECTION.

The in-line method invocation argument must be one of the following: SELF, EXCEPTION-OBJECT, NULL, the class name that is specified in the REPOSITORY paragraph, the data-item in the FILE SECTION, WORKING-STORAGE SECTION or LINKAGE SECTION, or the literal.

A class-name used as an argument in the in-line method invocation cannot be the class-name of a special class.

The @1@ statement for screen handling can only be used in the program definition.

The GLOBAL phrase cannot be specified in a USE statement with a class-name. The GLOBAL phrase is ignored.

An object modifier cannot be specified for a special class or for an object reference identifier that refers to a special class except an early-binding special class and '*COM(*OLE)'.

The class-name specified with the object modifier cannot be the class-name of a special class. Universal is assumed.

The object reference identifier in @1@ cannot refer to a special class.

The file organization is mismatched. The WRITE statement with the ADVANCING phrase is ignored.

The special class class-name cannot be specified in the USING phrase of the @1@ statement. The @1@ statement is ignored.

The predefined object identifier NULL cannot be use as an object identifier for the INVOKE statement.

The USING phrase identifier for the @1@ statement must be defined in a file, WORKING-STORAGE or LINKAGE SECTION.

The USING phrase identifier for the @1@ statement must be defined in the FILE, WORKING-STORAGE, LOCAL-STORAGE or LINKAGE SECTION.

@1@ cannot be specified for the identifier in the SEARCH statement. It is ignored, and the compiler skips to the next AT END or WHEN phrase.

@3@ cannot be specified for the @2@ phrase in the @1@ statement. The @2@ phrase is ignored.

The @1@ statement can only be used in the program definition. The @1@ statement is ignored.

@1@ can be used in the program definition. @1@ is ignored.

Predefined object identifier SELF cannot be specified in the KEY phrase of a SORT or MERGE statement.

Special register @1@ can only be used in the program definition.

A predefined object identifier or class-name cannot be specified in the USING phrase of the @1@ statement. The @1@ statement is ignored.

The object property cannot be specified in the RETURNING phrase of the @1@ statement.

'@2@' items are not valid for compile option @1@.

When an object reference in an INVOKE statement is an in-line method invocation or an object property, the object reference must refer to the class-name specified in the REPOSITORY paragraph.

OMITTED cannot be specified for the BY CONTENT phrase of the @1@ statement. The @1@ statement is ignored.

@1@ can only be used if the runtime code set is Unicode.

For the main program, the parameter specified for the USING phrase of the PROCEDURE DIVISION header should be only one group item that does not exceed 102 bytes, and the first subordinate elementary item must be a 2 byte binary item.

When the ENCODING clause is specified in the parameter described by the USING statement in the main program procedure division, then the encoding must be the same as the Alphanumeric data item specified in the compilation option ENCODE. The specified parameter will be disabled.

A class-name of early-bind special class must be specified for the object modifier which applies to the object identifier of the special class.

The left side of 'AS' must be an object identifier of special class, if a class-name of special class is specified for the object modifier.

Other optional phrase cannot be specified, if a class-name of special class is specified for the object modifier.

The ENCODING clause can be specified for an FD or SD data item, data description group item or elementary item as long as the item type is alphanumeric character, edited alphanumeric character, national, or national edited item. The ENCODING clause is disabled.

In the ENCODING clause of @1@, the alphabet name for encoding format @2@ must be specified. The ENCODING clause is disabled.

In the @1@ item of the MOVE statement where CONVERSION is specified, partial reference, function identifier, inline method calling and property name cannot be specified. The MOVE statement is disabled.

Alphanumeric data item or national item can be specified in the @1@ items of the MOVE statement where CONVERSION is specified. The MOVE statement is disabled.

A constant cannot be specified in the MOVE statement when CONVERSION is specified. The MOVE statement is disabled.

The alphabet name associated with the encoding cannot be described in the @1@ statement specifying COLLATING SEQUENCE. The @1@ statement is disabled.

There are multiple encodings that are mixed in the record display file definition, which is specified in printer device or display device in the destination type and printing file. Only one type of encoding can be specified in each alphanumeric data item and national item.

The FILLER cannot be omitted in the WITH FILLER phrase. FILLER is required.

It is not possible to include multiple encodings at the same time in the records of the Line file.

The length of the national hexadecimal nonnumeric literal of encoding UTF32 must be rounded off to a multiple of 8.

The program size is too large for this system. Compilation is terminated. Separate the program into smaller programs.

The program size is too large to specify the TRACE, COUNT, and/or CHECK options. The program should not be compiled with the TRACE, COUNT and/or CHECK options.

Item-name "@1@" contains a UNICODE peculiar character. Interactive debugger is treated as FILLER-item. Interactive debugger is treated as FILLER-item.

(@1@)@2@ statement is beyond the common range.

(@1@)@2@ clause is beyond the common range.

(@1@)Function-name in @2@ statement is beyond the common range.

(@1@)Mnemonic-name in @2@ statement is beyond the common range.

(@1@)Multiple file name in @2@ statement is beyond the common range.

(@1@)Identifier in @2@ statement is beyond the common range.

(@1@)Data-name in @2@ statement which defined in screen section is beyond the common range.

(@1@)Source reference format (free) is beyond the common range.

(@1@)@2@ paragraph in identification division is beyond the common range.

(@1@)Continuation of cobol words, numeric literals and picture character-strings is beyond the common range.

(@1@)This function-name is beyond the common range.

(@1@)Special register @2@ is beyond the common range.

(@1@)National literal is beyond the common range.

(@1@)Floating-point literal is beyond the common range.

(@1@)Bool literal is beyond the common range.

(@1@)Number of dimensions for subscripting is beyond the common range.

(@1@)Hexadecimal nonnumeric literal is beyond the common range.

(@1@)Level number 66 is beyond the common range.

(@1@)Level number 88 is beyond the common range.

(@1@)Symbolic character or literal or figurative constant with 'ALL' is beyond the common range.

(@1@)Reference modifier is beyond the common range.

(@1@)Qualification of data names is beyond the common range.

(@1@)National character is beyond the common range.

(@1@)In-line comment in this program is beyond the common range.

(@1@)Alphabetic-lower contained in '@2@' is beyond the common range.

(@1@)@2@ in ALPHABET clause is beyond the common range.

(@1@)Function name in ALPHABET clause is beyond the common range.

(@1@)Literal in ALPHABET clause is beyond the common range.

(@1@)Mnemonic-name of CHARACTER TYPE clause is beyond the common range.

(@1@)Nested IF statement is beyond the common range.

(@1@)Multiple literal of VALUE clause is beyond the common range.

(@1@)'Integer-1 THRU integer-2' of VALUE clause is beyond the common range.

(@1@)Multiple 'integer-1 THRU integer-2' of VALUE clause is beyond the common range.

(@1@)printing-mode-name in CHARACTER TYPE clause is beyond the common range.

(@1@)VALUE OF data-name is beyond the common range.

(@1@)Nested REDEFINES clause is beyond the common range.

(@1@)@2@ in PICTURE clause is beyond the common range.

(@1@)@2@ in USAGE clause is beyond the common range.

(@1@)CONSTANT SECTION is beyond the common range.

(@1@)@2@ in USE statement is beyond the common range.

(@1@)BASED-STORAGE SECTION is beyond the common range.

(@1@)Boolean operator @2@ is beyond the common range.

(@1@)Class condition @2@ is beyond the common range.

(@1@)Binary operator or unary operator @2@ is beyond the common range.

(@1@)Sign condition is beyond the common range.

(@1@)Logical operator or unary operator @2@ is beyond the common range.

(@1@)Abbreviated combination condition is beyond the common range.

(@1@)Complex-condition is beyond the common range.

(@1@)Condition-name condition is beyond the common range.

(@1@)Concatenation expression is beyond the common range.

(@1@)@2@ in ACCEPT statement is beyond the common range.

(@1@)Multiple procedure-name of ALTER statement is beyond the common range.

(@1@)GO TO statement omitted procedure name is beyond the common range.

(@1@)@2@ special register specified of IF statement is beyond the common range.

(@1@)Conditional statement in IF statement is beyond the common range.

(@1@)@2@ in INITIALIZE statement is beyond the common range.

(@1@)De-edit of numeric edited item in MOVE statement is beyond the common range.

(@1@)National edited item moved to national edited item in MOVE statement is beyond the common range.

(@1@)Numeric edited item moved to numeric edited item in MOVE statement is beyond the common range.

(@1@)@2@ special register specified of SET statement is beyond the common range.

(@1@)TO TRUE clause in SET statement is beyond the common range.

(@1@)Data item in START statement is beyond the common range.

(@1@)This relational character in START statement is beyond the common range.

(@1@)Multiple characters data item in INSPECT statement is beyond the common range.

(@1@)Multiple BEFORE/AFTER in INSPECT statement is beyond the common range.

(@1@)Multiple @2@ operand in INSPECT statement is beyond the common range.

(@1@)BLOCK CONTAINS 0 CHARACTERS is beyond the common range.

(@1@)'RECORD CONTAINS integer-1 TO integer-2' is beyond the common range.

(@1@)@2@ clause in CLOSE statement is beyond the common range.

(@1@)Line sequential file is beyond the common range.

(@1@)Subschema-name is beyond the common range.

(@1@)Nested program is beyond the common range.

(@1@)Number of USING phrase in CALL statement must not exceed 5.

(@1@)Number of formal parameters in USING phrase of PROCEDURE DIVISION header must not exceed 5.

(@1@)END PROGRAM header is beyond the common range.

(@1@)Sort-merge file is beyond the common range.

(@1@)Number of keys specified in ASCENDING/DESCENDING clause of SORT statement must not exceed 15.

(@1@)COPY statement in library text is beyond the common range.

(@1@)Text-name qualified by library-name is beyond the common range.

(@1@)Text-name constant is beyond the common range.

(@1@)File description entry of report file is beyond the common range.

(@1@)Report description entry of report file is beyond the common range.

(@1@)REPORT SECTION header is beyond the common range.

(@1@)CLOSE statement for report file is beyond the common range.

(@1@)OPEN statement for report file is beyond the common range.

(@1@)File description entry of presentation file is beyond the common range.

(@1@)@2@ in SYMBOLIC DESTINATION clause is beyond the common range.

(@1@)@2@ in ACCESS MODE clause is beyond the common range.

(@1@)Literal of file identifier in ASSIGN clause is beyond the common range.

(@1@)@2@ in ASSIGN clause is beyond the common range.

(@1@)Separator '->' is beyond the common range.

(@1@)Function name @2@ is beyond the common range.

(@1@)This function name is beyond the common range.

(@1@)Figurative constant NULL is beyond the common range.

(@1@)Data-name which defined in SCREEN SECTION is beyond the common range.

(@1@)'AS' for file identifier is beyond the common range.

(@1@) The source reference format (free) is not supported.

(@1@) A character excluded from the COBOL character set for the OSIV system is used.

(@1@) In the OSIV system, the length of @2@ must be 8 characters or less.

(@1@) In the OSIV system, @2@ must consist of alphanumeric characters starting with an alphabetic character.

(@1@) @2@ includes a hyphen. In the OSIV system, hyphens are replaced by '#' .

(@1@) The text-name constant is not supported in the OSIV system.

(@1@) An external-name for a program-name is not supported in the OSIV system.

(@1@) In the OSIV system, the quotation mark character must correspond to the specification of compile option APOST/QUOTE.

(@1@) The national literal contains characters that cannot be converted to a national character. The character is replaced by an underscore.

(@1@) Function-name '@2@' is not supported in the OSIV system.

(@1@) @2@ is not supported in the OSIV system.

(@1@) The concatenation expression is not supported in the OSIV system.

(@1@) @2@ of the object-oriented programming functions is not supported in the OSIV system.

(@1@) The IDENTIFICATION DIVISION header cannot be omitted in the OSIV system.

(@1@) The @2@ clause is not supported in the OSIV system.

(@1@) In the OSIV system, a sort-merge file can only specify a file-identifier in the ASSIGN clause.

(@1@) Line sequential files are not supported in the OSIV system.

(@1@) The SCREEN SECTION and screen description entry are not supported in the OSIV system.

(@1@) Named constants (level number 78) are not supported in the OSIV system.

(@1@) The type definition is not supported in the OSIV system.

(@1@) @2@ in the USAGE clause is not supported in the OSIV system.

(@1@) The @2@ phrase in the PROCEDURE DIVISION header is not supported in the OSIV system.

(@1@) The @2@ statement is not supported in the OSIV system.

(@1@) The @2@ phrase in the @3@ statement is not supported in the OSIV system.

(@1@) In the OSIV system, identifier @2@ of the ACCEPT statement specifying a mnemonic-name or function-name must be a fixed-length group item, an alphabetic, an alphanumeric, or an external decimal item.

(@1@) The @2@ statement of the screen handling function is not supported in the OSIV system.

(@1@) In the OSIV system, the length of the program-name specified for a @2@ statement must be 8 characters or less.

(@1@) In the OSIV system, @2@ is invalid as a program-name in the @3@ statement.

(@1@) The program-name in the @2@ statement includes a hyphen. In the OSIV system, hyphens are replaced by '#'.

(@1@) In the OSIV system, a JAPANESE check of the class condition is not supported.

(@1@) In the OSIV system, a relational character in the START statement is not supported.

(@1@) @2@ is not supported in the OSIV system.

Non-ASCII characters are included in the nonnumeric literal.

'@1@' cannot be used in this system.

Invalid data type of indicator variable.

Not executable SQL statement.

Right parenthesis corresponding to left parenthesis is missing near "@1@".

Format of national character literal is invalid.

Format of embedded variables name is invalid.

Format of nonnumeric literal is invalid.

C language comment cannot be specified.

Format of delimited identifier "@1@" is invalid.

SQL statement is invalid.

Format of host variable specification is invalid.

Format of argument list is invalid.

Cursor name is missing near "@1@".

SQL statement identifier name is missing near "@1@".

Stored procedure name is missing near "@1@".

Left parenthesis is missing near "@1@".

Connect target is missing near "@1@".

Connect object is missing near "@1@".

Disconnect object is missing near "@1@".

Connection name is missing near "@1@".

Username is missing near "@1@".

Target specification is missing near "@1@".

Query expression or SQL statement identifier is missing.

SQL statement variable is missing near "@1@".

Invalid specification after cursor name "@1@".

Invalid specification after SQL statement identifier "@1@".

Invalid specification after argument list.

FOR phrase can not specify in "@1@" statement.

Invalid specification of SQL statement variable in "@1@" statement.

Invalid specification position or method of FOR phrase.

Value in FOR phrase exceed its value in OCCURS clause.

Form of host variable is different.

Invalid form of indicator variable correspondence to host variable.

Invalid specification "@1@" after connect target.

Invalid specification "@1@" after connect object.

Invalid specification "@1@" after disconnect object.

Invalid specification after SQL statement variable.

Invalid specification after keyword "@1@".

Keyword 'OF' is missing just after keyword 'CURRENT'.

Keyword 'USING' or keyword 'INTO' is duplicated.

INTO clause is specified in query expression.

Embedded variable name "@1@" is not declared.

Invalid specification in item be subordinate to SQL statement variable"@1@".

Data type of SQL statement variable "@1@" must be character string type.

SQL statement variable "@1@" must be a fixed length character string.

Stored procedure name "@1@" is too long.

SQL statement is too long.

"@1@" is unsupported.

Values in OCCURS clause as each SQL statement variable are different. Minimun"@1@" is valid.

OPEN ERROR. FILE=$1.'$2'. $3

PROGRAM '$1' IS RECURSIVELY CALLED.

LAST STATEMENT IN USE FOR DEAD-LOCK EXECUTED. $1.

INVALID OPTION. $1.

INSUFFICIENT STORAGE AVAILABLE. '$1'

LIBRARY WORK AREA IS BROKEN.

NESTED PROGRAM IS RECURSIVELY CALLED IN PROGRAM $1.

CANNOT CALL PROGRAM '$1'. $2. $3

READ/WRITE ERROR. FILE='$1'. '$2'. $3

CLOSE ERROR.FILE='$1'. '$2'. '$3'

EXTERNAL DATA ATTRIBUTE ERROR. '$1'. '$2', '$3'

INVALID ENTRY INFORMATION. PGM=$1.$2

EXTERNAL FILE ATTRIBUTE ERROR. FILE=$1. PGM=$2,$3. '$4'.

USE FOR DEAD-LOCK NOT FOUND.

NO 'ON EXCEPTION' STATEMENT EXISTS, WHEN EXCEPTION OCCURRED ON '$2 $1' STATEMENT.

TWO OR MORE THREADS WERE EXECUTED IN SINGLETHREAD MODE.

PROGRAM '$1' CANNOT BE EXECUTED.

THREAD SYNCHRONIZATION FAILED. '$1' . $2

THE SINGLETHREADED PROGRAM CANNOT BE EXECUTED IN THE MULTITHREAD MODE. '$1'

CANNOT RUN PROGRAM WITH COMPILER OPTION '$1' IN THIS SYSTEM. $2

INVALID CHARACTER CODE OF THE FILE. '$1' $2

CODE CONVERSION LIBRARY CANNOT BE LOADED. $1 $2 $3

THE OPERATION INFORMATION ON THE PROGRAM. VERSION='$1' THREAD-MODE='$2' INIT-FILE='$3' SECTION='$4'

WORK AREA DESTRUCTION DETECTED. $1 $2 BRKADR=0x$3.

Forced terminated for the restriction. '$1' $2

THE PROGRAM NOT SPECIFIED THE PROGRAM WHICH SPECIFIED COMPILE OPTION RCS(UCS2,BE) WAS EXECUTED IN THE SAME PROCESS. '$1'.

DIFFERENT CODE SYSTEMS EXIST IN RUN-TIME ENVIRONMENT. '$1'

CANNOT REGISTER THE ENVIRONMENT VARIABLE '$1'.

CHARACTER CODE CONVERSION FAILED. $1 $2

CANNOT BE OUTPUT THE EVENTLOG TO COMPUTER '$1'. 'MSGNO=$2'

CANNOT REGISTER WINDOWCLASS '$1'.$2 $3

CANNOT CREATE WINDOW '$1'.$2 $3

RUN-TIME INITIALIZATION FILE'S PATH-NAME IS INVALID.

COBOL RUN-TIME SYSTEM IS NOT INSTALLED PROPERLY. FILE=$1.

FORCED TERMINATION. CODE=$1.

INSUFFICIENT STORAGE AVAILABLE TO CREATE '$1' OF CLASS '$2'.$3

CLASS '$1' CANNOT BE USED.$2.

CANNOT INVOKE METHOD 'CLASS=$2' $3.$4

EXCEPTION OCCURRED '$1'.$2

CANNOT LOAD CLASS '$1'.CODE=$2.$3

EXCEPTION OBJECT USE PROCEDURE IS RECURSIVELY CALLED.

THE STOP RUN STATEMENT CANNOT BE EXECUTED DURING EXECUTION OF FINALIZE METHOD. $1 .$2

INSUFFICIENT DATA ACCEPTED FROM SYSIN.

AWAITING A REPLY.

'$1'

STATEMENT SEQUENCE ERROR. STM=$1. PGM=$2. LINE=$3. RPT=$4.

SCREEN ITEM SIZE IS LARGER THAN LOGICAL SCREEN.

LOGICAL SCREEN SIZE IS TOO LARGE.

INVALID NUMERICAL VALUE ACCEPTED. $1

CANNOT ACCEPT/DISPLAY FROM SYSTEM CONSOLE. '$1' $2. $3

KEY DEFINITION FILE OPEN ERROR. FILE=$1. $2 $3

KEY DESCRIPTION IS INVALID. '$1' $2

WRONG CHARACTER STRING SPECIFIED IN CONTROL CLAUSE. '$1' $2

ERROR OCCURRED IN '$1' OF THE METHOD INVOCATION. '$2' '$3'

ERROR OCCURRED IN THE AS PHRASE. SPECIFICATION ON THE RIGHT SIDE OF THE AS PHARASE IS '$1' $2

CONFORMANCE ERROR OCCURRED IN THE SETTING OF THE SENDING OBJECT REFERENCE DATA ITEM TO THE RECEIVING OBJECT REFERENCE DATA ITEM. $1

ERROR OCCURRED IN A PROPERTY METHOD INVOCATION. '$1' 'NULL' $2

CANNOT INVOKE METHOD '$1' WITH THE ANY LENGTH CLAUSE SPECIFICATION. '$2' '$3' $4

INVALID JOBDATE FORMAT.

ERROR IN COLLABORATION WITH GENERALIZED LOG. '$1' '$2' '$3'

DISPLAY OUTPUT FOR EVENTLOG CANNOT BE WRITTEN TO COMPUTER '$1'. '$2' $3

TRANSCRIPTION OF $2th DATA FAILED. STATEMENT='$1' '$3' $4

INITIAL VALUE OF 'POINTER' PHRASE IS INVALID. STATEMENT='$1' $2

SOME CHARACTERS HAVE BEEN LEFT IN SENDING ITEM. STATEMENT= '$1' $2

TRUNCATION OF $1th DATA OCCURRED. STATEMENT='UNSTRING' $2

'$1' ($2) OPENED BY '$3'IS NOT CLOSED. $3

CLOSE ERROR DURING PROGRAM TERMINATION. PGM=$1. FILE=$2.

$1 ERROR. FILE=$2. '$3'. $4

MISSING ALLOCATION. FILE=$1. '$2' $3

INSUFFICIENT STORAGE AVAILABLE. STM=$1. FILE=$2. $3

INPUT/OUTPUT ERROR. STM=$1. FILE=$2. '$3'. $4

AT END CONDITION. STM=READ. FILE=$1. $2

KEY SEQUENCE ERROR. STM=$1. FILE=$2. $3

DUPLICATE KEY ERROR. STM=$1. FILE=$2. $3

RECORD NOT FOUND. STM=$1. FILE=$2. $3

BOUNDARY VIOLATION ERROR. STM=$1. FILE=$2. $3

NO-SPACE CONDITION. STM=$1. FILE=$2. $3

INVALID KEY CONDITION. STM=$1. FILE=$2. '$3'. $4

DEPENDING ON OBJECT VALUE IS OUT OF RANGE. STM=WRITE. FILE=$1. $2

STATEMENT SEQUENCE ERROR. STM=$1. FILE=$2. '$3'. $4

THREAD SYNCHRONIZATION FAILED. FILE='$1' FILE. '$2'. $3

CONTROL RECORD FORMAT ERROR. STM=WRITE. FILE=$1. '$2'. $3

USE PROCEDURE IS RECURSIVELY CALLED.

PS FILE ACCESS ERROR. CODE=$1.

ORDER CREATE PROCESS ERROR. STM='$1'. FILE='$2'. CODE=$3. $4

SYMBOLIC DESTINATION ERROR. FILE=$1.

CLAUSE '$1' ERROR. FILE=$2.

DUPLICATE FONT NAMES WERE FOUND. '$1'.$2

INSUFFICIENT STORAGE AVAILABLE TO PERFORM SQL.$1

ENVIRONMENT INFORMATION FILE ERROR TO PERFORM SQL. '$1'.$2

START ENVIRONMENT ERROR TO PERFORM SQL. '$1'. $2, $3

$1 ERROR. STM=$2. SERVER=$3. '$4'.

UNRECOGNIZABLE SQL STATEMENT WAS FOUND. $1

THE SQL STATEMENT CANNOT BE EXECUTED IN ACCORDANCE WITH THE ENVIRONMENT INFORMATION FILE. '$1' $2

ERROR OCCURRED BY OPENING THE ENVIRONMENT OF SymfoWARE TO EXECUTE SQL STATEMENT IN THE MULTITHREAD MODE. '$1'

THE NETWORK DATABASE FUNCTION CANNOT BE USED.

ACCESS ENVIRONMENT ERROR OCCURRED. SYS=$1,FILE=$2,BLK=$3,$4=$5

STOP RUN STATEMENT MUST NOT BE EXECUTED USING JMPCINT2.

CANNOT OBTAIN WINDOW HANDLE. '$1'.$2

INSUFFICIENT STORAGE AVAILABLE TO PERFORM SORT OR MERGE STATEMENT. $1

SORT OR MERGE STATEMENT ERROR. $1. $2

RELEASE STATEMENT CANNOT BE EXECUTED IN OUTPUT PROCEDURE. $1

RETURN STATEMENT CANNOT BE EXECUTED IN INPUT PROCEDURE. $1

RETURN STATEMENT CANNOT BE EXECUTED AFTER AT END. $1

SORT/MERGE LIBRARY CANNOT BE LOADED. $1 $2 $3

SORT/MERGE STATEMENT CANNOT BE EXECUTED IN AN INPUT/OUTPUT PROCEDURE.$1

THREAD SYNCHRONIZATION FAILED DURING THE SORT/MERGE STATEMENT. '$1'. $2

THREAD SYNCHRONIZATION FAILED. $1

GCB IS BROKEN.

LIA IS BROKEN.

RCB IS BROKEN.

DEBUG TABLE IS BROKEN.

INSUFFICIENT STORAGE AVAILABLE. FUNC=$1.

FILE CANNOT BE OPENED. FILE=$1. '$2' OPTION IGNORED.

FILE CANNOT BE OPENED. '$1' OPTION IGNORED. $2

THE VALUE OF ENVIRONMENT VARIABLE '$1' IS INVALID. '$2' OPTION IGNORED.

MAXIMUM SIZE OF THE FILE IS EXCEEDED. FILE='$1'. '$2' OPTION IGNORED.

THE VALUE OF ENVIRONMENT VARIABLE '$1' IS INVALID.

THE INVOKE OF THE $1 FAILED. '$2'. '$3'

THE COBOL DEBUGGER DID NOT RESPOND THOUGH PASSED THE TIME-OUT INTERVAL.

REMOTE DEBUG ERROR, CONNECTING CLIENT FAILED. $1. $2

REMOTE DEBUG ERROR, CLIENT WAS DISCONNECTED. $1

REMOTE DEBUG ERROR OCCURRED AT '$2' IN '$1'. $3. $4

FAILURE IN $2 PARAMETER OF THE '$1' METHOD. $3 $4 LINE=$5

FAILURE IN CALLING CONVENTIONS OR PARAMETERS OF THE '$1' PROGRAM. $2. LINE=$3.

FAILURE IN '$1' OF CALL STATEMENT. $2. LINE=$3.

SUBSCRIPT/INDEX IS OUT OF RANGE. $1. LINE=$2. OPD=$3 ($4)

REFERENCE MODIFIER IS OUT OF RANGE. $1. LINE=$2. OPD=$3.

ODO OBJECT VALUE IS OUT OF RANGE. $1. LINE=$2. OPD=$3. ODO=$4.

INVALID VALUE SPECIFIED. $1. LINE=$2. OPD=$3.

DIVIDED BY ZERO. $1. LINE=$2. OPD=$3.

LOGICAL ERROR.

FUNCTION $1 ERROR, ARGUMENT ABSOLUTE VALUE IS MORE THAN 3.53E+15.$2

FUNCTION $1 ERROR, ARGUMENT ABSOLUTE VALUE IS MORE THAN 1.0. $2

FUNCTION $1 ERROR, ARGUMENT VALUE IS OUT OF RANGE. $2

FUNCTION $1 ERROR, ARGUMENT VALUE IS INVALID. $2

FUNCTION ANNUITY ERROR, ARITHMETIC EXCEPTION. $1

ERROR OCCURRED IN THE '$2' METHOD OF THE SPECIAL CLASS '$1'. SCODE=$3 $4 $5 $6

INSUFFICIENT STORAGE AVAILABLE FOR THE '$2' METHOD OF THE SPECIAL CLASS '$1'.$3

FAILURE IN $3 PARAMETER OF THE '$2' METHOD OF THE SPECIAL CLASS '$1'.$4 $5

TYPE CONVERSION ERROR OCCURRED IN $3 PARAMETER OF THE '$2' METHOD OF THE SPECIAL CLASS '$1'.$4 $5

ERROR OCCURRED BY THE SPECIFICATION OF THE ELEMENT IN THE '$1' METHOD OF THE SPECIAL CLASS '*OLE-ARRAY'. $2

TOO MANY ITEMS WERE REGISTERED. SPECIAL CLASS=$1. $2

SPECIAL CLASS '$1' CANNOT INVOKE IN MULTITHREAD MODE. $2

INSUFFICIENT STORAGE AVAILABLE FOR TREATING THE SPECIAL CLASS '$1'. $2

THE ERROR WAS DETECTED IN '$1'. '$2'. '$3'. '$4'. '$5'. '$6'

THE START PARAMETER OF THE COBOL ERROR REPORT IS INVALID. '$1'

THE OUTPUT OF THE ERROR DETECTION MESSAGE TO COMPUTER '$1' FAILED IN THE COBOL ERROR REPORT. '$2'

THE ERROR OCCURRED IN THE COBOL ERROR REPORT. '$1'

FAILED TO ATTACH TO THE PROCESS: $1 ($2)

THE PROCESS IS TERMINATED DURING THE ERROR DIAGNOSIS.

DIAGNOSED AN APPLICATION WITH NO RESPONSE. '$1'

DIAGNOSED AN APPLICATION WITH NO RESPONSE, BUT FAILED TO OUTPUT A REPORT FILE. '$1'

WATCHED THE WRITING OF AN AREA. '$1'

WATCHED THE WRITING OF AN AREA, BUT FAILED TO OUTPUT A REPORT FILE. '$1'

THE ADDRESS OF THE WATCH AREA IS NOT SPECIFIED.

THE ERROR WAS DETECTED IN '$1'. '$2'. '$3'. '$4'. '$5'. '$6'

THE APPLICATION ERROR OCCURRED. '$1'. '$2'. '$3'. '$4'.