COBCH1001 - COBCH1020

• COBCH1001 Character other than *, D, /, -, or $ found in column 7. Blank assumed
  You might have mistyped one of the characters allowed in column 7. Your COBOL system cannot interpret the character in column 7, and has treated it as a space.
• COBCH1002 Continuation character invalid at this point. Blank assumed
  You have placed a hyphen in column 7, though your COBOL system is not expecting the syntax to be continued at this point. The continuation character is ignored.
• COBCH1003 First character of a continued literal not a quote. Quote assumed
  You have included a continuation character in column 7, but you have forgotten to start the continuation of the literal with a quotation mark. Your COBOL system assumes that the quotation mark is included.
• COBCH1004 Continuation character expected. End of literal assumed
  The literal in the previous line of source code is not delimited by quotation marks, so your COBOL system is expecting a continuation character in column 7, and a continuation of the literal. Your COBOL system has assumed that you meant to end the literal on the previous line.
• COBCH1005 Name ends in hyphen. Processed as written
  You have used a hyphen as the last character in a user-defined-name, which is against the rules of COBOL syntax. Your COBOL system has accepted this as a valid name, however, and has not changed the name in any way.
• COBCH1006 COBOL word contains more than 31 characters. Word truncated
  The name that you have specified is longer than 31 characters. Your COBOL system treats this as a name consisting of the first 31 characters of your original name.
• COBCH1007 VALUE literal size size1 > data item size size2. Literal truncated
  The literal you have specified in the VALUE clause is too long to fit into the data item. Your COBOL system inserts characters from the literal into the data item, until the data item is full.
• COBCH1008 DBCS literal must contain an even number of characters. Literal truncated
  All Double Byte Character Set (DBCS) symbols are two bytes (two characters) long. You have specified a literal that consists of an odd number of characters. Your COBOL system ignores the last, single character of the literal.
• COBCH1009 Closing delimiter for DBCS literal not found. Delimiter assumed
  You have not included the quotation mark to show the end of the Double Byte Character Set (DBCS) literal. Your COBOL system has assumed that you intended to end the literal at this point.
• COBCH1010 Nonnumeric literal has length of zero. One SPACE assumed
  The alphabetic or alphanumeric literal you have defined in your source code is empty, that is, you have a pair of quotation marks with no character between them. Your COBOL system has assumed that the literal contains one space character.
• COBCH1011 DBCS literal has length of zero. Length of one DBCS character assumed
  The Double Byte Character Set (DBCS) literal you have defined in your source code is empty, that is, you have a pair of quotation marks with no DBCS character between them. Your COBOL system has assumed that the literal is two characters long, and that it has a value of spaces.
• COBCH1012 DIVISION missing or misspelled. DIVISION assumed
  You have omitted the word DIVISION from a Division header, or you have spelled it incorrectly. Your COBOL system has assumed that DIVISION is what was meant.
• COBCH1013 SECTION missing or misspelled. SECTION assumed
  You have omitted the word SECTION from a Section header, or you have spelled it incorrectly. Your COBOL system has assumed that SECTION is what was meant.
• COBCH1014 Period missing. Period assumed
  You have omitted a period in a place where one is expected by the rules of COBOL syntax. Your COBOL system has assumed the period is present.
• COBCH1015 OCCURS integer-1 exceeds OCCURS integer-2. Zero is assumed for integer-1
  You have included the OCCURS integer-1 TO integer-2 DEPENDING clause in your source code, but the value given for integer-1 is greater than that for integer-2, which is against the rules of COBOL syntax. Your COBOL system has effectively changed the value of integer-1 to 0.
• COBCH1016 Expected SEPARATE before CHARACTER in SIGN clause. SEPARATE assumed
  You have incorrectly coded the SIGN clause because you have included the word CHARACTER, which is not required, but you have omitted the required word SEPARATE. Your COBOL system has assumed that you intended the clause to be SIGN IS LEADING (or TRAILING) SEPARATE CHARACTER.
• COBCH1017 REDEFINES ignored for 01 level item in File or Communication Section
  You have tried to REDEFINE a data item in the File or Communication Section but the data item is an 01 level item. Level 01 items for the same FD or CD automatically redefine one another.
• COBCH1018 VALUE clause not allowed here. Clause processed as comment
  You have tried to assign a value to a data item defined in the File Section or the Linkage Section. The VALUE clause is ignored.
• COBCH1019 Unsigned numeric literal expected. Sign ignored
  You have specified a sign where one is not expected, for example, you have used the AFTER ADVANCING +1 or BEFORE ADVANCING -2 clause to the WRITE statement. Your COBOL system ignores the sign, and treats the digits as a positive value.
• COBCH1020 Unsigned numeric field. Sign in VALUE clause ignored
  You have defined a numeric data item (that is, PIC 9) and you have tried to assign a signed number as its value. Your COBOL system ignores the sign you have specified. Where you are trying to move a number with a negative sign into a numeric field, the result is not as expected.

Parent topic: Messages COBCH1001 to COBCH1100

---

---